Form auto save problem

[deepaksharma]

Unless you have a reason that you must have consecutive numbers, then so what? If you can't have "missing" numbers, then sometimes those records are just saved without data, or flagged as "Rejected" or something that identifies them as being discarded. This can also point out where there may be issues with users using the system haphazardly.

You might be better off creating any numbers (assuming you can't just use an autonumber) at the end of the process; i.e. open the form without the number, create it upon save. This is usually the best method if the db is used in a shared environment.

Your suggestion is good but I have seen many sharing database programs made in SQL in many offices in which for example if you are going to make a bill then in that program the bill number is shown first and after that other data entry is feed.
Suppose at some time, for example, a user creates a bill of number 202 and at the same time on this program (which is shared on another computer) another user also creates a bill of number 202, then now the user who saved first When the user clicks on the button, his data will be saved and the user who later clicks on the save button will be shown an error message.
"this bill no. already exists"

[deepaksharma]

Hi Deepak

Main field 1 is the Primary Key set to Autonumber
Field OrderNumber - Number - LongInteger

You can then set the Before Update of the Form to use the DMax Function to Add new OrderNumbers

hi mike,
According to you this needs to be set in the Before Update event i.e. I was making a mistake by coding in the Form Load event? This means that you and Micron are trying to explain the same thing that the offer number should be generated only after the data entry is completed

[mike60smart]

Yes that's right.

You can also do it on the AfterUpdate of the OfferDate ie

If Me Dirty then Me.Dirty = False
The use the DMax to get the next OfferNumber

[Micron]

now the user who saved first When the user clicks on the button, his data will be saved and the user who later clicks on the save button will be shown an error message.
"this bill no. already exists"

That does not happen if the number is created at the last moment. Think about it.

[deepaksharma]

That does not happen if the number is created at the last moment. Think about it.

ok i'll take care of that....

[deepaksharma]

That does not happen if the number is created at the last moment. Think about it.

i refer this question https://www.accessforums.net/showthread.php?t=88729