Corrupted or not a valid Access DB - ALL THE TIME

[newbieinmd]

Ok, I have a small (12,000 record) DB that is opened by about 15 users with no security setup (all users in as admin). I am using a autoexec form startup so they don't get the DB window.

3 - 4 times a day I will get a user who tries to enter the MDB file and will get the above error. Then I have to get everyone out of the DB and enter it myself and do the recommended rebuild. This ALMOST always fixes it, but sometimes it will blow away the FRM they use all the time.

Here are the steps I have taken to prevent it:

1. Replaced all NIC cards in w/s with Intel Pro/100+ cards because some of the older cards had tempermental connections.

2. Tried using VBA code to disable bypass key, but that blew the whole DB up within 3 hours and I had to redo the whole darn thing and import the night before backup.

3. Begged it to stop doing it.


Any more suggestions?

 

[Rohdem]

I don't know what operatings systems you use on your network or what version of Access you are using, but we have had problems in the past with Windows 2k corrupting an Access 97 database repeatedly. We finally just put NT back on the machines. There is a utility available on Microsoft's website called LDBView that will tell you who has left the database in a suspect state. This is how we discovered that it was our 2 Windows 2000 machines that were causing the problem.
Mike Rohde
rohdem@marshallengines.com

 

[newbieinmd]

Mike,

Thanks for the info. ALL clients and servers in my network are running Win2k. I can't imaging that Microsoft would have developed an OS that wouldn't work with their own Database (yeah right).

Thanks for the help.

Kurt