Why does a record-locking file remain after I close database?

[wvushawk]

When I close my database, sometimes a record-locking file remains. This
forces me to copy the database to another folder to continue my editing. The
record-locking file, (64KB) remains even if I delete my original .mdb. What
can I do to stop this from happening?

 

[Jerry Whittle]

Make sure that you, and any other users, have Read, Write, Create, and Delete
privileges to the folder that holds the database file.

 

[wvushawk]

thank you for that input. I am, however the only user for this database. Many
times I just open the data base and close it and am ok. Again, sometimes,
when I close the database, the record-locking information file stays open.
The next time I try to open it, it shows read only. Then is when I have to
copy the db to another folder to begin editing again.

 

[Marco Pagliero]

thank you for that input. I am, however the only user for this database. Many
times I just open the data base and close it and am ok. Again, sometimes,
when I close the database, the record-locking information file stays open.
The next time I try to open it, it shows read only. Then is when I have to
copy the db to another folder to begin editing again.

If you are sure that you are the only user and that you don't open
twice the same mdb mistakenly:

The obvious solution would be to delete the record-locking file. If it
refuses to delete, it means that some part of Access is still active
in memory. Check the Task Manager. If you see Access there, try and
kill the process. After that it should be possible to delete the
record-locking file. If not, try and log out and log in again or even
to reboot. If then you can delete the record-locking file, it proves
that some module remains active in memory after closing the mdb.

I remember that there was this problem in the past (something about
writing "if a then" instead of "if a = true then"), so if this is your
case write again.