Could not Save;Currently locked by another user

[MartyO]

We have MS Access 2003, SP1 and SP2 users, user FE's linked to BE on a
server.

Two users accessing the same record, we're getting "Could not Save;Currenlty
locked by another user", instead of getting the friendly message that lets
you handle record locking gracefully. It's a memo field that they are
editing.

The strangest thing is that we are only getting this message on one
particular record. I've rebuilt the form, the table, deleted the record and
copied it back in.

Any ideas?
Thanks in advance for your help.
Marty

 

[Jerry Whittle]

Open the database and go to Tools, Options, and Advanced Tab. Check that the
Default Open mode is Shared and the Default Record Locking is 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.)

Possibly it's a corruption issue. Memo fields corrupt too easily. Have you
tried a compact and repair?

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[MartyO]

Thanks Jerry. These are good articles. I've tried almost all of the
suggestions but nothing is working so far. I'll keep at it.

Question: If I converted my backend to SQL Server, would that be a step in
the right direction in taking care of record locking errors, and memo field
woas?

Thanks!
marty

 

[Pieter Wijnen]

yes & no
Part of the problem is that Access & MS SQL use page locking instead of
record (or field locking!) that Oracle does
which means you're normally hogging (locking) more data than you think.
the easist way out AFAIK is to use a timer to save/discard the data if the
user has hogged it to long

NMH

Pieter

 

[Pieter Wijnen]

yes & no
Part of the problem is that Access & MS SQL use page locking instead of
record (or field locking!) that Oracle does
which means you're normally hogging (locking) more data than you think.
the easist way out AFAIK is to use a timer to save/discard the data if the
user has hogged it to long

NMH

Pieter

Thanks Jerry. These are good articles. I've tried almost all of the
suggestions but nothing is working so far. I'll keep at it.

Question: If I converted my backend to SQL Server, would that be a step
in
the right direction in taking care of record locking errors, and memo
field
woas?

Thanks!
marty

--