locked tables?

[Jacko]

Hi All,
I have a database installed on a network drive and has been working fine, recently though users are getting errors when trying to access it, they can get the switchboard up but when they try to access a certain form that has data from a certain table they get an error saying that the table is locked and that another user has it open, even when there in no one else in the database, the database is not split to backend/frontend and i dont know why the errors comming up or how to remedy it...any ideas/help appriciated.

thanks

 

[The_Doc_Man]

One of the pitfalls of shared DB's on a shared disk is that if any of your users just happens to turn off the PC (or it crashes), a file with a type of .LDB will be left dangling. This is the lock database. It should have the same name as your .MDB or .MDE file. Normally, if you exit from Access, this file is deleted if you are the last one in it. (Whoever leaves the room last, turn out the lights!)

If no one (including YOU) is in the database and you still have a .LDB file, delete it. Then try your form again to see if that fixes the problem.

 

[Jacko]

Thanks Doc,
I had realised this and deleted that file and then tried it out hopeing problem solved, and it appeared so, skipped about and grinned only to find next day when i went to go in again same error, checked who had ownership of the lbd file, and it was me! and yet i shut all day night before * puzzled *

 

[PearlGI]

I've experienced a similar problem to the one you describe.

I had a form that was used to import a large data set into an existing table. But sometimes, not always, this process returned the error 'record locked - in use by another user'. This other user was always me .
I knew I was the only user and I also knew I wasn't logged in elsewhere.

After much experimenting I discovered that this problem only ever occured if the database was run from the NT network and not if I tried it from a local drive.

In the end the only way round this was to open the db as exclusive whenever I wished the run the import.

Is this an NT issue? Who knows. It only ever occured on this particular table and I've used the same procedure on other db's with no problem.