Could not update, currently locked

eramirez

Registered User.
Local time
Today, 17:18
Joined
Dec 10, 2007
Messages
17
Hi

I am using an old version of an Access database (2000) which I split into a back-end (tables only) and front-end (forms, etc). I saved copies of the FE database on multiple users computers. There are ~10-15 users entering data at the same time through their FE db. Many of the users are getting this message, "Could not update, currently locked". I did some research online and from what I gathered it could be a combination of using Access 2000 and record-locking properties (something about Access not locking a "record" per se, but locking a "page" which may include mulitple records. Let's assume I can only use Access 2000 and I don't completely understand what page locking is.

does anyone have suggestions on how to reduce the number of times "Could not update, currently locked" pops up? It's a little frustraing for the users and slows down data entry.

I thought splitting the original database would solve this or least minimize, but I've run out of solutions.

Any help would be greatly appreciated!:confused:

Thanks
Enrique
 
Hi

I am using an old version of an Access database (2000) which I split into a back-end (tables only) and front-end (forms, etc). I saved copies of the FE database on multiple users computers. There are ~10-15 users entering data at the same time through their FE db. Many of the users are getting this message, "Could not update, currently locked". I did some research online and from what I gathered it could be a combination of using Access 2000 and record-locking properties (something about Access not locking a "record" per se, but locking a "page" which may include mulitple records. Let's assume I can only use Access 2000 and I don't completely understand what page locking is.

does anyone have suggestions on how to reduce the number of times "Could not update, currently locked" pops up? It's a little frustraing for the users and slows down data entry.

I thought splitting the original database would solve this or least minimize, but I've run out of solutions.

Any help would be greatly appreciated!:confused:

Thanks
Enrique

See if these help. http://www.tek-tips.com/viewthread.cfm?qid=1209150

http://support.microsoft.com/kb/331594
 

Users who are viewing this thread

Back
Top Bottom