![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
My application uses A2002 with up to 8 concurrent users with record level locking on open. The site is remote from my office. From time to time, one of my users encounters record locks (with the crossed out circle appearing in the record selector). No one is editing the current record at the time, but I'm assuming that it is caused by another user editing a related record in a linked table in the underlying query. Is there any way to determine which user and/or which edited record(s) is causing the lock? Also, is there any chance that a network system setting could have an affect? |
#3
| |||
| |||
|
|
On Thu, 24 Dec 2009 09:07:22 +1000, "Bob Darlington" bob (AT) notheredpcman (DOT) com.au> wrote: You're using a very strict locking setting. Isn't Optimistic Locking good enough? It is for 99% of the applications out there. Access locks a data page at a time, which may hold more than one record. No you cannot, although some error messages include at least the machine information: "... is locked by ... machine <machinename>..." -Tom. Microsoft Access MVP My application uses A2002 with up to 8 concurrent users with record level locking on open. The site is remote from my office. From time to time, one of my users encounters record locks (with the crossed out circle appearing in the record selector). No one is editing the current record at the time, but I'm assuming that it is caused by another user editing a related record in a linked table in the underlying query. Is there any way to determine which user and/or which edited record(s) is causing the lock? Also, is there any chance that a network system setting could have an affect? |
![]() |
| Thread Tools | |
| Display Modes | |
| |