Make A Process Wait while another process is running in Network

Moore71

DEVELOPER
Local time
Today, 00:53
Joined
Jul 14, 2012
Messages
158
Hi,
Please I just bug into this problem on my small access application being used by 2 individuals using the same shared Application on a network. The puzzle is when both of them update the same item in a one table, one freezes while the other may scale through.
My request here is any code that can make one system to wait for the other if any of the system is already processing the same item in the table


Thanks a million
 
Are both users using the same copy of the Access app simultaneously?
Or do you have a split database and ,if so, does each user have their own copy of the FE?
 
Yes, it's a shared app.
Each user has a copy of the FE. They are only collaborating at the Back-End (BE), I mean one table sets (DB)
 
I think /hope you mean its a split app with each user having their own copy of the FE.
Assuming that is the case, check your record locking settings
 
I think /hope you mean its a split app with each user having their own copy of the FE.
Assuming that is the case, check your record locking settings


It's a split Application.
I checked the record Locking is Shared not Exclusive
 
It is possible for the app (overall) and the queries or code within it to have different locking properties. I.e. Access has a default setting if you don't specify something, but any query can override the default. If you are using a recordset operation, that can also override any DB locking defaults that might be set.

Look specifically at the thing doing the update to that shared table, regardless of whether it is a query or a recordset operation. Whatever it is, briefly describe it for us and, in particular, if you have selected explicit record locking options, explain what was set and where.

In theory, unless your network speed is slow enough to count bit rate by hand, you should see no more than a millisecond blip even if two users are working on the same record.

Look ANYWHERE in the DB for anything that might set "Pessimistic" locking because that is an easy way to bring on the behavior you described. But that also isn't the default for most normal record operations.
 
On the same lines, record locking can be set generally in Access Options - client settings but also set individually in each form / query.
In each case the choices are No locks / All records / Edited Record

Also
Optimistic locking is when you check if the record was updated by someone else before you commit the transaction. Pessimistic locking is when you take an exclusive lock so that no one else can start modifying the record. You cannot combine optimistic locking with the automatic retry.

See also https://www.quora.com/What-is-optimistic-locking-vs-pessimistic-locking
 
Okay thank you all soooooo Muuuuuuuch.
I will go to the client office and try it out for her. Then I'll get back to when I am thru with her later.


Thanks a million
 

Users who are viewing this thread

Back
Top Bottom