Form record lock

[Nymandus]

My table has the primary key set to autonumber incremental index (no duplicates)

do I need my form where all the data entry happens to have record locks in the properties?

right now set to no locks
the other options are all records or edited records.

would having it set to no locks lead to a possible problem with the shared database and a couple users getting the same primary key and only the last one to click save is foudn in the table?

any help would be greatly appreciated.


my database is split to FE and BE
I moved everyone's FE onto their personal desktops.

 

[Pat Hartman]

Unless you are having some specific problem with contention, I would leave the lock settings alone. The default is no locks. That is referred to as "optimistic" locking since the record isn't locked until someone actually starts to change it. You can see this happen. Have two computers open a form on the FE and navigate to the same record. Make sure the form is showing the record selector. Turn it on for this test if it is off for this form. When userA starts typing in a control, a pencil will appear in the record selector on his computer. On userB's computer, a circle with a line through it will appear in the record selector to indicate that some other user is editing the record. The first user to save will be allowed to save his changes. The second user will get an error message warning him that the record has been changed and giving him three options.

Since in most applications, it is rare that two users will want to update the same record at the exact same time, most people never see this confusing error message but you should always teach people about it and tell them to choose the option to discard their changes. You want them to retrieve the record again to see what change was made before they make their change.