Doesn't any one know anything about record locking?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bob Parr - 11 Dec 2003 15:12 GMT

The only other post here about record locking, along wiht mine have not been
answered. If there is another way to handle this issue please tell me.
Here are my problems:

When I lock a table and then try to access data from the same instance of
the database that locked it, I get an error that it is locked. Is this
right. If so how can I get around it?

Also I never got an answer to this:

I have a database that is being shared by several users. I want to lock a
row in a table when it is being edited. I have the "open databases with
record-level locking" option set, but when I test, opening the recordset
with:

Set currentrec = db.OpenRecordset(qstr, dbOpenDynaset, dbDenyWrite)
currentrec.LockEdits = True
or
Set currentrec = db.OpenRecordset(qstr, dbOpenDynaset, dbDenyWrite,
dbPessimistic)

the whole table is locked. I get an error 3262

Any ideas what I am doing wrong?

Bob

Reply to this Message

Scott McDaniel - 11 Dec 2003 16:53 GMT

It's been a while since I've dealt with this, but IIRC dbDenyWrite locks the
entire table regardless of what options you have set ... try changing the
lock to something less restrictive.

Take a look at the MSDN information provided here (which I found in about 30
seconds by Googling on "ms access dbdenywrite dao"):

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deo
vrlockingshareddatabyusingrecordsetobjectsinvba.asp

> The only other post here about record locking, along wiht mine have not been
> answered. If there is another way to handle this issue please tell me.
[quoted text clipped - 15 lines]
> or
> Set currentrec = db.OpenRecordset(qstr, dbOpenDynaset,

dbDenyWrite,

> dbPessimistic)
>
[quoted text clipped - 3 lines]
>
> Bob

Reply to this Message

Glenn - 11 Dec 2003 21:50 GMT

> The only other post here about record locking, along wiht mine have not been
> answered. If there is another way to handle this issue please tell me.

8<

Hi Bob,
I just found out myself how frustating the record-locking stuff can be.
Reduced to its essentials, my application consists of one table in which
several users can enter/edit/delete their OWN records.
Simple, Access should have dealt with it on its own. It didn't :(

I followed the manuals, perused the examples as good as possible.
It didn't work: the blasted thing kept page-locking or even table-
locking $#@!
workaround upon workaround : no joy...

Till I entered the magic/correct keywords in the Microsoft KB and it
churned out these results

ACC2000: Access Database Does Not Use Record-Level Locking When Started
from a Windows Shortcut
http://support.microsoft.com/default.aspx?scid=kb;en-us;238258

PRB: Jet 4.0 Row-Level Locking Is Not Available with DAO 3.60
http://support.microsoft.com/default.aspx?scid=kb;en-us;306435

ACC2000: Record-Level Locking Does Not Appear to Work
http://support.microsoft.com/default.aspx?scid=kb;en-us;225926

for me it was q238258 that did it. One pc on the network had been
overlooked during several (all?) upgrades and had not SR1 installed.

Once the offending machine sorted out (in fact kicked out), the record-
locking worked.

---

posting a message on usenet is not guaranteed to reveal the answer.
Most often it will, though, thanks to the very helpful people roaming
these places.
Or your question has been asked already in the past.
Google & MS KB are invaluable, you just need some luck with the
keywords.

Last resort, sleep on it, you'll find it tomorrow :)

HTH
glenn

Reply to this Message