Unrecognized database format

[MoiraT]

There is a lot on the site about this error but not one that matches my problem exactly. I have a backend database on a Win2000 server (Access2000 format) and I have 4 users with a RUNTIME Access2000 front end. About once a week they get "unrecognized database format" error on the backend and they are unable to repair because they only have runtime versions (is that true?. The backend was originally created in A97 and converted to A2000. I had Compact on Close set on the backend but that seemed to make no difference. These are my references set in Access:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.6 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library

Any ideas on how to stop this error occuring, please?
Thanks

 

[KarMac21]

If you are running Access 2000 then you should have a reference to the Microsoft Access 9.0 Object Library not the 10.0 library. I believe that reference is for Office XP.

Everything else looks correct though.

Shane

 

[oharab]

The most common reason for a corrupt database is dodgy network cards! You may have to do a bit of research trying to find the dodgy one though.
Are your front end files installed on the users hard drives? If not, then that is something you should do straight away.
To let your users repair the back end, they can either go through the ODBC manager, just choose to add a new Access file, then choose the repair option, or you could try createing a shortcut to the backend file with the repair switch:
c:\program files\Microsoft office\office\1033\msaccess.exe c:\PathTo\Database.mdb /repair

though I'm not sure if this will work with your runtime file.

Good luck! I've been where you are now & it's the most distressing thing imaginable!

Ben


----------------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

"Where are all the stupid people from...
...And how'd they get so dumb?"
NoFX-The Decline
----------------------------------------------

 

[MoiraT]

Thanks for all your help. It is frustrating but I think we may have found the answer and I hope it helps others in this situation. We disabled opportunistic record locking on the Windows 2000 server (running SBS) and so far the problem has not re-occurred ... keeping our fingers crossed