Currently Locked Error Msg

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an Access 2000 dbase shared among approximately 50 users. One
particular form bound to one large table (used by only about 15 users total),
constantly gets the "Can't Update, Currently Locked" error message.

I've searched these newsgroups and tried all the solutions that apply from
the (mostly older) posts and KB articles - to no avail. The database is
split (BE & FE are both run off the server though) and the problem has
recently become worse, meaning it happens once or twice a day. I have to get
everyone using that form out before the lock is released. I've even tried
getting the users out one by one to try and determine WHO had the lock and
what they may have done to cause it.

Could this be a "real" lock on the whole table/record/page in Access? It
seems to me it's got to be caused by something else. I suspect a "Duplicate
Record" button (created by the Access wizard) on that form may have something
to do with it. That's not a functionality *I* would have built into the
database but they rely upon it heavily now.

I've played with the record lock settings in the Options dialog endlessly to
no avail.

Any suggestions?
 
Hi, Sandie.
Any suggestions?
Click to expand...
The database is
split (BE & FE are both run off the server though)
Click to expand...

If the users are sharing the same form in the same file all the way across
the network, then don't be surprised that you have record locking problems.
Every user should have a copy of the front end on his workstation to avoid
corruption, prevent record locking issues, improve performance, enable
updates, et cetera. The Microsoft Access development team has identified the
number one cause of corruption is multiple users sharing an Access database
across the network, so even if you weren't experiencing locking issues, you
should still prevent the users from sharing the front end. For more
information on splitting the database properly, please see the "Split the
Database" tip on the following Web page:

http://www.Access.QBuilt.com/html/gem_tips1.html#SplitDB

The first user who opens or connects to a database dictates how record-level
locking will be used for all subsequent users until the LDB file is deleted.
So if the first user opens his database file with page level locking,
everyone else uses that level, too, until everyone is out of the database.
Ensure that the "Open databases with record-level locking" option is checked
in each user's copy of the front end, and in the back end. If the records of
this table contain memo fields, realize that only page level locking will be
used, despite your settings.

For more tips on improving the performance of your database in a multiuser
environment, please see Access MVP Tom Wickerath's article, "Implementing a
Successful Multiuser Access/JET Application" on the following Web page:

http://www.Access.QBuilt.com/html/multiuser_applications.html

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.
 
Back
Top