could not update; currently locked

pma111
pma111 used Ask the Experts™
on
We have 2 users of an access 2010 application who get an error ''could not update;  currently locked'. I have tracked down the row in the table that these forms are accessing and can see no issues at all, e.g. signs of corruption. Is there anything else that can be done. There are a few forms that show/update date in this particular row, unsure really what may cause this, but as its affecting multiple users each with their own FE the common denominator being that row, what can be done.
If I connect to the backend of the system and try and manually edit a single column in the record it gives the same error.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012
Commented:
<<If I connect to the backend of the system and try and manually edit a single column in the record it gives the same error.>>

 With everyone out of the DB, delete the .LDB file in the directory where the BE DB resides.

 If you cannot delete it, then a lock is being held, probably by someone that exited Access with Ctrl/Alt/Del.   In that case, the simplest thing to do is reboot the server.

 If that's not easily doable, there are other means to clear the lock.

Jim.

Author

Commented:
Yes we don't have admin rights over the server, and its a shared file server used by a few hundred staff. Any other techniques.
Jim Dettman (EE MVE)President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012

Commented:
<<Yes we don't have admin rights over the server,>>

Don't think you'll be able to clear the lock without admin rights.  You need access to computer management:

Region-Capture.jpg
 and close the file.

 This only works though if the user is a network user (sounds like it is).   But if this is a terminal services server, then the access is local.  For that, you need to use Process Monitor to find the handle for the file and close it manually.

Jim.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
I'll speak to the server team then. But your suspicion is the cause of the error is a lock I presume.
Jim Dettman (EE MVE)President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012

Commented:
With everyone out of the app, the .LDB file should disappear.

 If it's still there and you cannot delete it, then a lock is still being held.

Jim.

Author

Commented:
Trying to track it down now. It would be a network user. It wont be an RDP session, we do have a citrix access gateway but it logs them onto a citrix server. Nobody bar IT access the file server via RDP.

Author

Commented:
Turned out someone connected to the system via our VPN which crashed and for whatever reason access did not release the lock. Once they re-established a connection again to the file again via VPN it all worked again and the record could be amended.
Jim Dettman (EE MVE)President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012

Commented:
That will do it.   With a JET/ACE backend, all the db processing is carried out on the client side.  The server only acts as a file sharing device.  So any abnormal disconnect is a problem.

 Any remote users you have should be setup with RDP.

Jim.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial