access 97 error CURRENTLY LOCKED BY USER ADMIN

[katherine25]

We have an access97 database on a shared server that is accessed by 15 people using Windows NT operating system. Everyone has access to it using teh same password. Recently we have experienced increasing locking problems such that the users are unable to exit from the program. The error messages upon trying to close are:
OUT OF MEMORY
THE SAVE OPERATION FAILED
COULDN"T SAVE;CURRENTLY LOCKED BY USER ADMIN ON MACHINE__________
I have tried compacting the datbase, compiling it and decompiling it. I have shrunk it from 25mb to 8mb but the problem has continued.
Any suggestions?
thanks,
katherine

 

[Hap007]

Katherine,

One sure cause for access not to terminate when you try to exit happens if a programmer, using VBA code, creates a temporary recordset in code and fails to close and set the record set to nothing before exiting the sub routine.

If you do this, you risk leaving these recordsets in memory and access will not close when you try to exit. This was a huge problem with Access 97, I do not know if later versions of Access still have this problem.

If this is your problem, then if you repeat these called VBA routines and exit leaving recordsets open, you indeed may run out of memory also. Who knows, maybe this is causing record lock issues also, but this is usually caused when a change to a record and someone else tries to change the same record or a record real close to the record (Physical record) in the database. Access locks Pages, not records so when you change one record there is a remote possibilty that you may lock another record that is located close to the first record.

Hope This Helps,
Hap
Access Add-on developer

http://www.fcs-software.com

-

 

[lcwin]

Katherine,

We have exactly the same problem with our Access97 application (which has 4 users using a Windows 2000 server). Like you, we started experiencing these same locking problems such that users cannot exit from the program, with precisely the same error messages. We've tried many things to fix it - one of which was making sure that all recordsets are closed, as was recommended - and nothing's worked! If you, or anyone else, learn of a solution, I'd love to hear about it!

Thanks,
Lisa

 

[psemianonymous]

http://groups.google.com/groups?q=o...tabases.ms-access&hl=en&lr=&ie=UTF-8&oe=UTF-8

There are some similar problems. I browsed and found some things to try:
--you have a corrupt database. Try a compact & repair to fix it. If that fails, check the FAQ below for more fixes. Looks like you've done this already.

--Dangling LDB file. After everyone is out of the database, check to see if the LDB file still exists. Attempt to delete it. (Delete all the LDB files)


--this is actually a record-locking problem. Not likely.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm