MDW File Keeps Getting Corrupted!!

[SteelersFan]

I have an access database at work that is split between the forms/reports/queries (front end) and data tables (back end). Both are located on a file server. I have a shortcut (read only) that is accessed by the people wanting to open the database. The MDW/Security file is located in the same directory as the databases and is named different. Sporadically, the database will lock up with the message saying someing like, "the security file is opened and can't be accessed....".

This database is a high profile database here at work. Lots of people are in it at the same time (maybe 20 or so people will have it opened at the same time - Is that a lot?).

It is a real pain to fix this problem, because you have to:

1) Try to get everyone out of the database (found a neat trick that you an drag the ldb file to a note pad document and release and you can see who is int it by PC name and user name).

2) Friday, I had all the users out but names STILL showed up in the ldb file. I had to restore the file with a different name and re-set the properties in the shortcut to point to this new file.

This is becoming a real issue at work and causing some to think this database is crap. I need to rectify this problem ASAP.

Any thoughts?


Dave

 

[engkeong]

MDW file corruption

HAd a similar set up here at where i worked

We got round the issue by creating a batch which copied a copy of the mdw file to the personal drive and starting the database using the /workgrp command switch

Downside to that is that any changes in password will not be reflected in the original mdw file. To cope with that, we have a password reset option which fires up the database using the original mdw file purely for password resetting purposes.

A bit of recoding required but save a lot of time once the corruption stops