Access over a network??

[Kieran]

I need help, i have a database that is being accessed over a network by more than one machine. It has been working fine for a while, now it keeps coming up with an error at startup saying that there is an error and then asking if we want to fix it. After doing this, certain fields cannot be updated and then database never is the same again. i also notice that the database is about halved in size...........i need help.....any ideas what could be causing problem............using access 2k and xp.


Thanks for any help.....

 

[Autoeng]

Someone is probably not exiting your database before turning off their machine which is locking it up. When you get the error message select that you do not want to correct the problem. Use Explorer to look in the directory for any files ending in .ldb. If any exist that means that someone is logged into the datbase or left the database without properly shutting down. Now start the database back up, select yes to correct the problem and scold your users .

Autoeng

 

[bone head]

Thats interesting i have just put a databae on a network and will remember that, as i am sure it may well crop up.

Just one quick point do you actualy delete the .ldb file after you have found it.

Cheers

 

[Autoeng]

You won't be able to delete the ldb file because it will say it is use. You will have to do any of a number of things to get it to release. First try to auto repair by trying to open the true file that the ldb has locked (mydatabase.mdw is locked by mydatabase.ldb). This will usually release the lock. Second try rebooting the users machine that has the file locked. How do you know who locked the file? You can read the .ldb file with Notepad and it will list the user OR when you try the auto repair it should list the user. Third reboot the server.

Another thing that I have found that locks a db is that the user exits properly then tries to reenter immediately (like within 1 or 2 seconds). By trying to reenter so quickly the db didn't have a chance to release and it locks up.

Autoeng

 

[The_Doc_Man]

This problem can be exacerbated by some users not having proper access rights. All users who run Access on this shared .MDB file absolutely MUST have certain rights to the directory. If they do not, you run the risk of this situation.

Users must be able to do : File Scan, File Read, File Create, File Delete, File Update, and File Write. Depending on the nature of your file server, these ability names may differ from what I listed.

You need Scan to identify files.
You need Read to read the .MDB and .LDB (if the latter exists)
You need Create if you are the first person to open the .MDB because YOU have to create the .LDB file.
You need Delete if you are the last person to close the .MDB because YOU have to delete the .LDB file.
You need Update to be able to modify the contents of the .LDB file once it is open and you start actions that imply locking.
You need Write to be able to fill in the contents of the .LDB file if you are the first creator of it.

Of course, Access itself will do these things for you, but in network security terms, Access "rides" your own privileges. That is, Access is not defined to run as Admin. It gets its rights from your individual rights profile. Which is why ALL of your users need this set of rights. And it does not matter whether they are "read-only" to the database. They will NOT be read-only to the .LDB file.

Now, this relates to your problem if someone is UNABLE to delete the .LDB file when they exit out of Access. So before you rattle the saber over their heads, verify that they have rights to do what is necessary in that directory. If they do, THEN go ahead with the saber rattling. Then, it will be deserved.

 

[Kieran]

thanks

thanks for the advice i'll have another look at it.........

 

[Pat Hartman]

The .ldb file can be deleted if the SERVER is rebooted. That will free the DOS file lock which is what is preventing the delete.