Avatar of Pau Lo
Pau Lo
 asked on

could not update; currently locked

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.
Microsoft OfficeMicrosoft Access

Avatar of undefined
Last Comment
Jim Dettman (EE MVE)

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Jim Dettman (EE MVE)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Pau Lo

ASKER
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)

<<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.
Pau Lo

ASKER
I'll speak to the server team then. But your suspicion is the cause of the error is a lock I presume.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Jim Dettman (EE MVE)

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.
Pau Lo

ASKER
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.
Pau Lo

ASKER
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.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Jim Dettman (EE MVE)

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.