Repost: Form does not release locks with record-level locking

  • Thread starter david epsom dot com dot au
  • Start date
D

david epsom dot com dot au

I have a form with "Record Locks" set to "No Locks".
The database setting for "Default record locking" is "No Locks"
The database is opened from the open database dialog.


When "Open databases using record-level locking" is enabled,
the bound record remains locked after it is saved, and I
am unable to use an update query.

When "Open databases using record-level locking" is NOT
enabled, the bound record is unlocked after it is saved,
and I am able to use the data in an update query, to update
another table.


Is this normal? If so, is there a way ensure that the database
is not opened with record-level locking?

A2K SP3, Jet SR8, Win2K/WinXP

(david)
 
T

Tom Wickerath

When "Open databases using record-level locking" is enabled,
the bound record remains locked after it is saved, and I
am unable to use an update query.

This is likely if you are using DAO, because you do not *really* get record-level locking with
this option, at least according to this KB article:
PRB: Jet 4.0 Row-Level Locking Is Not Available with DAO 3.60
http://support.microsoft.com/?id=306435


Tom
________________________________


I have a form with "Record Locks" set to "No Locks".
The database setting for "Default record locking" is "No Locks"
The database is opened from the open database dialog.

When "Open databases using record-level locking" is enabled,
the bound record remains locked after it is saved, and I
am unable to use an update query.

When "Open databases using record-level locking" is NOT
enabled, the bound record is unlocked after it is saved,
and I am able to use the data in an update query, to update
another table.

Is this normal? If so, is there a way ensure that the database
is not opened with record-level locking?

A2K SP3, Jet SR8, Win2K/WinXP

(david)
 
D

david epsom dot com dot au

I guess that indicates that my dao code is working with
record-locked records, because the databases involved
were already open in Access. Except that the records
are of course indexed, and the indexes at least are page
locked.

The question is, why does the bound record remain locked
after it is saved? What can you do to unlock a bound record?
Why does this have anything to do with a users record-locking
option? And can anything be done to over-ride that option
for a database opened in Access?

(david)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top