Can't find 'MSysDb' - how to recover?

[WaltW]

I just tried to open a MS Access 2000 database, and got an error message that said something like "could not find object 'MSysDb'". Access then wouldn't even open the database. I have no idea what happened or what caused this. But is there a way to repair the database and use it again? This is a critical database (aren't they all?), and I would hate to have to revert to a backup copy ...

Thanks for any help offered!

Walt

 

[willir]

MSysDb ???

I checked the system objects for Access 97 and 2000 - MSysObjects and other hidden tables, but not MSysDb. Searched at the file level - not there also.

I then successfully created a table called MSysDb. I should not be able to do this if the object existed since every object in Access has to be unique. (For example, you can not use the same name for a form and a table)

I am not in a position to repeat the test creation on a password protected system or a replicated database -- away from my normal environment.

This leads me to suggest that the object may have been created manually, or is a component that the system creates when incorporating security or replication, or something new to XP.

If your database opens up and incorporates coding, hold down the SHIFT key when openning the database to prevent any macros or code from running.

It is possible that importing the table from a backup may work, or opening up a backup copy and import the up-to-date tables.

Good luck on this one.
Richard

Richard

 

[WaltW]

Thanks for the response, Richard. Unfortunately, I can't open the database at all - I just get the error message, then it stops. I can't import from it into another database either - same error message pops up. I even tried the "JetComp.exe" program (compacts a database without having to open it), and got an error message on that too. So it looks like I'll have to revert to a backup of the database from a couple days ago ...

Again, thanks for your efforts!

Walt

 

[RoyVidar]

Hi!

This might be database corruption.

This faq Corrupt Microsoft Access MDBs FAQ has a lot of info concerning corruption, symptoms and how to deal with it. See the Coruption symptoms link there, and you'll find this as one of the messages. Also check out MakeItSo's FAQ705-4683.

During the last years, I've been fortunate enough to have been able to resolve all my corruption issues using the /decompile option, in stead of importing objects. It's described here Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times. You might try that.

There's also a utility from Microsoft, that I've never tried, Jet Compact Utility Available in Download Center.

Roy-Vidar