Question "could not update currently locked" msg access 2010

raymondchen21

Registered User.
Local time
Yesterday, 16:13
Joined
Oct 18, 2015
Messages
12
Hi,

If anyone had similar issue, I hope you can share your solution with me.

I have been running a database at work for a couple months now that is used by over 150 people. Yesterday I split the back-end file into four back-end files because the original BE file is getting too big.

After I did the splitting it was working fine till this morning when it stopped working. A couple users started getting an error msg that was something along the lines of "Could not update currently locked". I consulted with several database people at my office, but no one knew what the issue was.

But then two hours later the error msg disappeared and people could use the database again.

FYI, before I did the split I also ran into a similar issue but it only happened once.

I am starting to suspect that someone must have opened the database incorrectly so the file got locked, but this is just me speculating as I'm not really sure what the actual cause of the issue was.

If you happen to know the cause of this issue please do share. I want to know how to fix it if I ever come across it again.

Thanks for your help.
 
set record locks to none, this will allow access to control record locking.
 
I checked the fe and all be files after the error msg disappeared. Under the option setting, default record locking is set to no lock. Is this the setting you are referring to?
 
maybe something is happening because you have 4 back end files.

how big is the back end?

if it's that big, and you have 150 users, I expect a Jet/Ace backend is not the right solution.
 
set record locks to none, this will allow access to control record locking.
2010

I checked the fe and all be files after the error msg disappeared. Under the option setting, default record locking is set to no lock. Is this the setting you are referring to?
 
yes, have you set each backends default open mode to shared also.
 
yes, have you set each backends default open mode to shared also.

I also checked. They all set to default open mode to shared.
I just attached a pic of the setting. I don't know if you can see it.
 

Attachments

  • Capture.PNG
    Capture.PNG
    19.7 KB · Views: 203
maybe something is happening because you have 4 back end files.

how big is the back end?

if it's that big, and you have 150 users, I expect a Jet/Ace backend is not the right solution.

The size of three of my BE files is average 30K to 40K. The main BE file's size is the largest and it changes because I run delete and append queries on it every day. I always make sure it won't reach to the limit. If Jet/Ace backend is not the right solution? Do you know what is the most feasible solution for me?
 
where is the be located, can anybody can see its location and access it.
 
where is the be located, can anybody can see its location and access it.

I left them in a folder in the common server. Yes people can see it and access it, but hardly people will go into the folder except me.
 

Users who are viewing this thread

Back
Top Bottom