access database lock file not being updated correctly

T

Tiger Heli

I am running a DB on a share drive with a few users having access. This DB
is not split but does have user accounts. I have recently noticed that the
lock file doesn't have correct or current information. Sometimes when I open
the file in notepad, it will show me as logged in multiple times or will show
users as logged in who I have seen close the application. Other times it
will clear correctly. A few times the database will be locked an hour after
I closed the application after using it in exclusive mode. Another admin for
another similar DB has told me that he has been getting messages (which I had
gotten a while back that suddenly stopped) regarding "MYSYSDB" or "SYSDB" or
something to that affect errors. Assistance would be appreciated.
 
T

Tom

I ALWAYS split the database and giving each user a front end file.
I believe this is the best way to avoid problems. It has never been
necessary for me to study the contents of the lock file.
 
T

Tony Toews

Tiger Heli said:
I am running a DB on a share drive with a few users having access. This DB
is not split but does have user accounts.
Click to expand...

As others have stated you should split the MDB.

I have recently noticed that the
lock file doesn't have correct or current information. Sometimes when I open
the file in notepad, it will show me as logged in multiple times or will show
users as logged in who I have seen close the application. Other times it
will clear correctly.
Click to expand...

This is normal. Opening the .ldb file using notepad will show you
both who's currently in the database and some of the workstations
which were in the database. When a person exits Access their
workstation name and Access login id, Admin unless you are using
Access security, are left in a "slot" or record in the ldb file. This
slot or record may get overwritten the next time someone enters the
MDB depending on what slot or record is available previous to it in
the ldb file.

Determining the workstation which caused the Microsoft Access MDB
corruption
http://www.granite.ab.ca/access/corruption/workstation.htm
A few times the database will be locked an hour after
I closed the application after using it in exclusive mode.
Click to expand...

What do you mean by locked? The ldb file is still around? You can
rename it?

Another admin for
another similar DB has told me that he has been getting messages (which I had
gotten a while back that suddenly stopped) regarding "MYSYSDB" or "SYSDB" or
something to that affect errors.
Click to expand...

Now this is a sign of corruption.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Top