How avoid adding new invoice number

[MoGrace]

Re: How avoid adding new invoice number

Once a record is saved be it the parent or child you cannot cancel the action and will have to delete. You could try the
Ask Save form event but I have never had any luck with it.

Also using the OnExit event is too late to send a cancel command. The CanSave event might work and you could prompt the user first then issue the cancel command. But again if the browse record has been entered and saved, so was the header - as soon as the cursor entered the browse.

[test37]

Re: How avoid adding new invoice number

Invoice form is not saved but the header part is over and the form is still open but cursor is in browse and after delete browse line its not saving in Invoice_Item table that is functioning well. On this form I have exit button in that push event I don't want to save header part just cancel everything how do I do that ?

[MoGrace]

Re: How avoid adding new invoice number

Have you looked at the Alpha Sports example? The invoice.set they use for the Invoice form has referential integrity set for the line items to cascade changes and deletes. There are buttons for adding or deleting an item that you could copy and edit to add or delete the parent which will then also delete the items by default.

To automate this behavior so that no user interaction is needed will require that you test the data entry for whether a valid invoice has been entered or not. And that can get quite complicated. Perhaps you could supply us with an example of your tables and form?

[test37]

Re: How avoid adding new invoice number

I am attaching screenshot my Invoice.set Please suggest me if that is require and changes.
ScreenShot.jpg

[MoGrace]

Re: How avoid adding new invoice number

I see you have looked at the Alpha Sports example so here is an invoice you can import there and then take a look at the CanExit, OnExit and Btn_Exit scripts. Copy to your desktop and then under forms in the control panel right click to import the file.

AS_invoice2.a5pkg

Edit:
Slight change to the CanExit script should be:

DIM mode as c
DIM shared commit_flag as L
mode = parentform.mode_get()
'If the form is in Enter or Change mode, prompt user to save the changes before closing the form
if mode = "ENTER" .or. mode = "CHANGE" then
	response = ui_msg_box("Save Invoice","Do you want to save this Invoice?",36 )
	if response = 7 then
		sys_send_keys("{ESC}")
		end
	else
		parentform.commit()
		commit_flag = .t.
	end if      
end if

If the user has not saved the invoice then the prompt allows him to choose before closing if he uses the red X.

[test37]

Re: How avoid adding new invoice number

Hi Robin,

I took your lots of time for small things but I am learning Alpha and certain basic things are new for me.
How do I open or import .a5pkg file ?

[MoGrace]

Re: How avoid adding new invoice number

Copy to your desktop and then under forms in the control panel right click to import the file.

[Nick Oldfield]

Re: How avoid adding new invoice number

Have you looked at the Alpha Sports example? The invoice.set they use for the Invoice form has referential integrity set for the line items to cascade changes and deletes. There are buttons for adding or deleting an item that you could copy and edit to add or delete the parent which will then also delete the items by default.

To automate this behavior so that no user interaction is needed will require that you test the data entry for whether a valid invoice has been entered or not. And that can get quite complicated. Perhaps you could supply us with an example of your tables and form?

Using referential integrity is the easy way to do this. If you delete the parent, any children are automatically deleted. To be consistent, you need an exit button that asks if the user want to save. Or a cancel and exit button. I use this approach for all my sets (quote, sales order, invoice). Then you don't need to worry whether a child has been saved automatically when you leave the row.

[Al Buchholz]

Re: How avoid adding new invoice number

Referential integrity is an easy way to go but with it's limitations.

When the parent/child is viewed, all the child records are locked.

The locking of the records increases network activity.

There is a limit of 255 child records to each parent record.

Like all tools - choose wisely and from an informed position.

[Nick Oldfield]

Re: How avoid adding new invoice number

Referential integrity is an easy way to go but with it's limitations.

When the parent/child is viewed, all the child records are locked.

The locking of the records increases network activity.

There is a limit of 255 child records to each parent record.

Like all tools - choose wisely and from an informed position.

Yes, none of those are issues for me.

[Al Buchholz]

Re: How avoid adding new invoice number

Yes, none of those are issues for me.

Great. But is it an issue for Harshad?

[Nick Oldfield]

Re: How avoid adding new invoice number

Maybe. Now you have pointed them out, maybe he will respond.