Access lockfile and inaccessability to db

[reynolmm]

I currently have a db with multiple users with each having access from their
desktop. This morning I cannot access the db exclusively although I know
nobody is actually in the db as I've physically walked to each machine to
inspect. The author of the lockfile has closed all applications and powered
the desktop down with no success.

How do I delete this lockfile and gain exclusive entry into my db?

I've tried deleting and had the user try deleting with no success. I get
the error message that the file is in use by the application. My last ditch
effort would be to have all users power their desktops down in an attempt to
break the network connection to the db. If that won't work, then I will need
to contact IT in order for a restore procedure.

 

[John Vinson]

I currently have a db with multiple users with each having access from their
desktop.

That's unwise, for exactly the reason you're experiencing. Consider
splitting the database. See

http://www.granite.ab.ca/access/splitapp/

This morning I cannot access the db exclusively although I know
nobody is actually in the db as I've physically walked to each machine to
inspect. The author of the lockfile has closed all applications and powered
the desktop down with no success.

How do I delete this lockfile and gain exclusive entry into my db?

I've tried deleting and had the user try deleting with no success. I get
the error message that the file is in use by the application. My last ditch
effort would be to have all users power their desktops down in an attempt to
break the network connection to the db. If that won't work, then I will need
to contact IT in order for a restore procedure.

You may need to reboot the server. This makes the IT people very
unhappy but it might be necessary...

While you're at Tony's site (above) check out his Corruption FAQ, it
has some suggestions related to your problem.

John W. Vinson[MVP]

 

[reynolmm]

Thanks for the assistance. I was able to clear the lockfile by copying the
db. For whatever reason, it cleared itself when I did this. I will certainly
look into splitting the db. Thanks for your help and suggestion.
Mike