How avoid adding new invoice number

[test37]

I am beginner to V10. I checked Alphasport example.
-When I click on create invoice and immediately after that I click on exit even though its adding invoice number. (If user will click on by mistake create invoice and without any changes if press exit button in that case it should not add new invoice number.)

Please guide me how can i avoid adding number?

Waiting for reply

Thanks
Harshad

[Ray in Capetown]

Re: How avoid adding new invoice number

I just took a quick look at Alphasports.
In my opinion the exit button should be better labelled "Save and Exit" according to the code on the button. That is what it does.
Use the form's "X" to exit without saving.

To have the exit button not save, you would need to edit the xbasic code to remove the line with Commit() and then add a button to do the commit (save).

[test37]

Re: How avoid adding new invoice number

Is there any way to check is user updated or not? If user updated in that case we can ask question you had done changes, do you want to save ?
Please advise me how do I check user done any change in invoice form or embedded browser or not ?

[Stan Mathews]

Re: How avoid adding new invoice number

If the user has begun any changes the form will be in change mode.
If yo collect the initial field values with alltext_initial(), I (on fetch event) think, you can compare that to the state of the fields at the later time.

[test37]

Re: How avoid adding new invoice number

I am beginner, if you can provide a small code example that will be very helpful for me.

Thanks

[Stan Mathews]

Re: How avoid adding new invoice number

http://wiki.alphasoftware.com/ALLTEXT_INITIAL+Function

[Ray in Capetown]

Re: How avoid adding new invoice number

In the Alphasports example because a new invoice number is generated upfront, the alltext method will always be .t.
This type of approach though easy to implement, is not quite so simple to control issuing of numbers.
There have been a few discussions on just this precise topic, anyone remember the last one?

Here is an example for you to try, see how it works for your purpose.

if alltext() <> alltext_initial()
	msgbox("Changes were made")
end if
 'this will immediately be true because of the auto increment number - for illustration only. Remove the above lines once you see it.
if mode = "ENTER" .or. mode = "CHANGE" then
	if msgbox("SAVE","Save this invoice number?",UI_YES_NO) = 6
	   parentform.commit()
	   'Check to see if the record was successfully saved
	   if parentform.mode_get()<>"VIEW" then
	      ui_msg_box("Unable to save your changes","Please correct and save, or discard your changes", UI_STOP_SYMBOL)
	   end if
	else
		cancel()
   end if
end if
'Close the form
parentform.close()

For learning purposes. The above is the code that exists on the EXIT button with the addition of a few lines, a condition for the message box prompt and the alternative CANCEL()

[johnkoh]

Re: How avoid adding new invoice number

Ray,

This one.

if alltext() <> alltext_initial()
'	msgbox("Changes were made")
message_text_var = <<%text%
Changed were made.
Do you want to close without save now?

OK - Close without Save records.
Cancel - Save and Close.

%text%
end if
'this will immediately be true because of the auto increment number - for illustration only. Remove the above lines once you see it.
 
msg1_result=ui_msg_box(title_var,message_text_var,UI_OK_CANCEL+ UI_FIRST_BUTTON_DEFAULT+ UI_QUESTION_SYMBOL)
'Test to see which button on the message box was pressed....
If msg1_result = UI_OK_SELECTED then
	'just close it
	sys_send_keys("{esc}")
	'cancel()
	parentform.Close()
else
	'save it	
	parentform.Commit()
	parentform.Close()	
end if

[MoGrace]

Re: How avoid adding new invoice number

There are so many ways to do a similar thing in Alpha. If you have buttons on the form for adding a new record, allowing change to an existing one and for closing the form, and you set up the form with restrictions so that the user MUST use your buttons; then you can include all sorts of checks for the data before the expected action is taken. Otherwise if you let the user use the red X to close the form, then you need to include your data check in the CanExit event for the form.

BTW Stan, those alltext and alltext_initial functions are new to me and I plan on using them - Thanks!

[Ray in Capetown]

Re: How avoid adding new invoice number

Robin.
Note that alltext() is essentially an SDI function and in a form based on a set, only applies to the first table record.
IMO you are better off sticking to the MODE methods for form control since they are in your vocabulary.

[MoGrace]

Re: How avoid adding new invoice number

Thanks Ray, I will keep that in mind.

[test37]

Re: How avoid adding new invoice number

Hi Ray/Stan/John/Robin,

Thanks a lot for sample of code that is working fine and I am happy with that.
One more question for Invoice form.
If I change in header part that is working fine and exit without saving.
But if I add one line in browse and in that case if I would like to cancel how can I exit without saving that line in browse?

Thanks in advance
Harshad Ganhi

[Ray in Capetown]

Re: How avoid adding new invoice number

You should maybe use a different strategy.
There are different ways to implement this but it involves not creating the actual numbered invoice in this set. Only preparing it. The incrementing number can be continued - only for continuity but not used.
At some point you will either ;
1. accept the invoice and copy all to the actual invoice set and allocate the next invoice number,
2. delete it from the preparation set or mark it rejected and discarded

[MoGrace]

Re: How avoid adding new invoice number

Once the cursor leaves the browse the item is saved, so you would have to programmatically delete the record. You could add a CanExit event that prompts the user if they want to save their changes or not, and if not, delete the records in the browse. Otherwise add a a button to the form or to the browse that will delete the record manually. Or do both...

EDIT:
Oops, I see Ray beat me to it. Personally I like the Quickbooks style of doing things which seems more intuitive to me. Give the user a button or a hot key that works consistently with all the forms. Then he can add, change, save or delete records as needed.

[test37]

Re: How avoid adding new invoice number

Thanks a lot for reply immediately.

For browse I will put the message by right click and delete the row, thanks for suggestion.
In browse after adding browse line I am able to delete without any problem so its not adding row in Invoice_Item table.
But its adding record on header table.

On exit button push event I wrote
sys_send_keys("{esc}")
cancel()
parentform.cancel()
browse1.cancel()
parentform.close()

Eventhough its adding record on header table Invoice. How to avoid that. Is this above code right ?