Question Access 2003 database has no .ldb file but MMC says users have it open!

[BrainstormUK]

I have an Access 2003 database that is kept on a network drive which is used by a process to export the data to another directory. When I try to delete it to put a new version there it says there's a sharing violation and it's being used by other users... but it isn't open - no .ldb file. I go see my network admin person who checks with MMC and he says there're 3 (say) ... users using the database - how's this possible???? Even if you link to a table and open it it opens an ldb on the network file and if a process is downloading a table from it it only table a matter of secs so I'd imagine any connection is held open just for that time rather than hours...days etc
Hope someone can point me in the right direction.
Cheers

 

[Len Boorman]

Check network permissions for those persons that system says have the database open.

L

 

[BrainstormUK]

Why check permissions of those perportedly in the database? If they were in the database would not there be an .ldb file?

 

[Len Boorman]

Listen

They are in the database.

There is not an ldb file

Those are known facts.

So you need to start somewhere to establish why ?.

All users of a database should have full access rights to the network folder in which the database resides.

So a scenario

User A opens database ldb file created
User B opens database but this user does not have modify rights and therefore ldb file is not updated
User A leaves database and because they have full rights including delete the ldb file is deleted because there is no entry for User B.

So no ldb exists but there is probably something in the mdb file that says file is in use.

So when you have established that users have the correct permissions you eradicate one potential cause.

Thats why you check permissions

You asked for advice.

L

 

[BrainstormUK]

Too true and thanks... just finding it hard to consider users in the database but there being no ldb... However I think I may have found the reason in that the users of another application, it appears, update their applications from the tables in this database but not by linking but by using some mapinfo basic routines.... probably remotely opening the mdb in code and copying the tables out to their apps. I can image the scenario that if the code isn't written very tightly then the variables may not be explicitly closed and so my database remains in an 'open' state all the while their have their application open.

 

[Len Boorman]

In my experience assume nothing and start at what appears to be the base point.

Then expand the investigation.

In your case it was Users and as you have found you appear to have some rogue users.

Explain to then what they are doing and get them to link correctly.

The situation you describe is a bit naughty. The professional approach would be to discuss the linking with you before actually doing it, test it and then go live. The testing would have revealed the problem.

Glad you seem to have a solution

L