Record Locking issues

[ThomasAJ]

My database is split into front and back ends. The front is compiled into an
MDE.
They both sit on a W2003 machine and the front end is used by 4 or 5 users.

I want to stop people making simultaneous changes to the same record in the
same form so I set Options/Advanced/Default record locking to Edited record
AND checked Open databases using record-level locking ON THE FRONT END.

The back end has (I just noticed this minutes before this post and this may
be the problem) Default record locking as No locks AND UNchecked Open
databases using record-level locking.

OK so I go into the same record in the same form from two PCs and I can
still make a change on PC2 whilst PC1 had made changes. I leave the record on
PC2 so when I then leave PC1 I get the "someone else has made
changes...message".

I check the record locking settings on PCs 1 and 2 and they BOTH have "No
locks".
Are they picking up the settings from the back-end?
Should the front AND back have the same settings.
I cannot find any documentation on this scenario.

 

[mscertified]

This is normal behaviour for Access.
What you can do is to have a 'pending update' column in your table.
When someone reads the record they first check this column, if its not null,
someone has the record and you can issue a message with the userid who has
the record. If the column is null, you fill in the user's userid and
immediately save the record. When you finish your updates, you clear the
column and then immediately save the record.

Dorian

 

[ThomasAJ]

Sorry but that technique has been discredited many many years ago for a
multitude of reasons.

When you say "This is normal behaviour for Access." I'm not clear what you
mean.
1. Record locking does NOT work at all.
OR
2. Record locking does not work in the front/back end scenario I described.
OR
3. ...