Could not update Currently Locked

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

Guest

I am experiencing this error on a shared 2003 database that has about 25
users at any given time. I have the database set to "open database record
level using record level locking" and the default record lock is "no lock",
yet I keep getting this message. Also in Access 97 whenever I got this
message it usually told me who has the record locked, however with 2003 it is
not. Any suggestions?
 
1. All users of the database must have at least read, write, and modify
privileges to the folder holding the database file. Not just the database
..mdb file, but the entire folder.

2. Open the database and go to Tools, Options, and Advanced Tab. Set the
Default Open mode to Shared and the Default Record Locking to Edited Record.
(While you are in the Options area, go over to the General tab and turn off
Compact on Close and Name AutoCorrect. Trust me on this.)

3. You can also get this error if someone has a form, report, etc., opened
in design view. Early versions of Access would allow someone to make design
changes while others are using the database; however, newer versions limit
this ability. It's another good reason to split the database so that you can
do development on a copy of the Front End and put it into production easily.
Sure beats working midnight shift when the users aren't around!

4. It’s possible that someone has manually opened the database exclusively.
In that case go to the folder holding the .mdb file and open up the same
named .ldb file in Notepad. You might be able to read which users are in the
database and locked it. Apply 2â€x4†as necessary to user. However that should
give a "file already in use" error. To stop this from happening create a
shortcut for each user on their desktop or off the Start button. It should
list the target as the database file and look something like:
"P:\Databases\Database File.mdb"

5. To open exclusive use the following in a shortcut: Make sure that the
path, version of Office, and database name are right:

"C:\Program Files\Microsoft Office\Office11\MSAccess.exe" "C:\Program
Files\Microsoft Office\Office11\Samples\Northwind.mdb" /excl

You can also open up Access by itself; go to File, Open; select your
database in the Open dialog box; then go to the lower right of the dialog box
and change Open to Exclusive.
 
still can't find the solution of problem :coluld not update,currently locked
normally I have front end and beck end, on both sides the parametars
-shared-record lockin-edited record and open using record level locking
in normal situation (multi user,app.10-15) if two users try to use same
record conflict dialog is appear and I use marking of row as not free to use
but acording to microsoft there is a bug in microsoft access
http://suport.microsoft.com/kb/331594/en-us
when the same user try to do a second edit attempt in a transaction
this means that the same user blocking themselves, not other user
microsoft have the solution of that problem - use microsoft OLEDB driver for
ODBC (MSDASQL) instead of Jet 4.0
but I have difficulties to use anthying else but Jet, simply it is new for
me I don't know what to expect and I think that it can't be done with access
on the both side(as database part and frontend)
is there any other solutions ,like some version of me.undo if the user is
start editing and this proces is blocking
I must say that this error cause blocking this computer and nothing can be
done other then wait or end task ,problem is when one computer often have
this error and then he cause other users to slow down their transaction
because the mdb on back end is to busy?
sorry,for my english
I use Your pages to gathering information and it is very usefull for me ,so
thank you for that
greetings from croatia


Korisnik "Jerry Whittle" napisao je:
 
I'm confiused; different experts seem to give different opinions on this:
For normal, multi-user databases, should the Tools | Options | Advanced
settings be:
Default Open Mode: Shared
Default record locking: Edited Record
Open Databases using record-level locking: Yes
or
Default record locking: no locks
?

And if this is a front-end + back-end database, what should these settings
be on each?
(I am trying to prevent the "could nto update, currently locked" error that
occurs often when my users try to add records to a table.)
Thanks!
 
I use both version, no locks and edited records and it seems it’s no big
difference in my case
I wryly don't understand why one workstation gets 20 times error and same pc
just two or neither
Users are constantly in the same table in two different forms (reports,
filters, and querries running every second)
All users doing just update data not adding; adding data works fine (by
query following schema every morning)
hope that someone give some idea one day


Korisnik "David H." napisao je:
 
Back
Top