Can't open my project file (couldn't fine 'MSysDb')

[Sokkheng]

I can't open my project file it always show the message as below
The Microsoft Access database engine could not find the object 'MSysDb', Make sure the object exists and that you spell its name and path name correctly.
my Microsoft Access file version 2019Pro Plus
How to solve this problem.
Thanks
Sokkheng

 

[Pat Hartman]

The database is corrupted. You can try a compact or a decompile. You can also try to import the objects into a new database. Otherwise, hope you have a backup.

 

[The_Doc_Man]

I'm in full agreement with Pat.

The MSysxxx tables are internal system tables used to describe the database contents. If you are missing an MSys table you have a damaged database.

It is POSSIBLE to try to recover this. First make a copy of the file and put it aside in a safe place, because the recovery effort might destroy the file you are trying to recover. Once you have a copy you can try to do a Compact & Repair (C&R) by opening Access and directing it to do a C&R of the file in question. HOWEVER, I suspect that the C&R operation will fail because what it does requires it to open the file to examine the Access infrastructure. Which I suspect it cannot do.

Pat's second suggestion is a decompile. Instructions for that can found on the linked page. (Scroll down a little to find the DECOMPILE part.)

Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption

Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption

fmsinc.com

Again, I'm going to guess from that error message that your problem isn't compiled code but rather is damaged infrastructure. The bad news is that this might be unrecoverable, requiring you to step back to your last available backup copy. (Events like this are WHY you make backup copies.) If you have no backup copy, I hope you took good notes when you build the project because you'll be starting from scratch.

 

[theDBguy]

I hope you have a good backup, 'cause you might need it. Good luck!

 

[isladogs]

MSysDb is not a system table. It is a system object used to manage the database itself.

If it really is missing or corrupted, then your database cannot be recovered and a backup is your only possible solution
Neither compacting nor decompiling will be possible in this situation

 

[drimals]

I can't open my project file it always show the message as below
The Microsoft Access database engine could not find the object 'MSysDb', Make sure the object exists and that you spell its name and path name correctly.
my Microsoft Access file version 2019Pro Plus
How to solve this problem.
Thanks
Sokkheng

Try compacting and repairing the Access database. If that doesn't work, contact Microsoft support.

 

[Gasman]

Try compacting and repairing the Access database. If that doesn't work, contact Microsoft support.

Did you not read post #5?

 

[The_Doc_Man]

@Anny12 - your advice is unlikely to help. In order to check for hidden objects, you must first open the DB in order to explore it - which cannot be done if the attempt to open the DB results in the MSysDB error. A different version of Access is unlikely to do any better at opening the app. And the ability to import into a new database requires that Access open the old DB to explore it for elements. ALL of your suggestions need to get past that fatal "Cannot find MSysDB" error.

Thanks, Colin, for reminding me that MSysDB is an object, not a table. It's been a while since I explored that particular area.

 

[isladogs]

@Anny12
Just to add to the above comments which I fully agree with
Both of the posts you have made so far have been on old threads with no recent posts. Both are about database repairs and look to me like you have either taken them from CoPilot or more likely from the articles by a well-known company that heavily advertises its products for repairing Access and other applications

Their articles always start with general advice before building to comments like your final sentence:
If the above methods will not work for you, it means the data is severely corrupted, then you can try some third-party access repair tools.

My strong suspicion is you are making a thinly disguised attempt to promote that product but are currently unable to post links as a new member.
If that is your intention, you will find your account gets permanently blocked for spamming this site

 

[GPGeorge]

@Anny12
Just to add to the above comments which I fully agree with
Both of the posts you have made so far have been on old threads with no recent posts. Both are about database repairs and look to me like you have either taken them from CoPilot or more likely from the articles by a well-known company that heavily advertises its products for repairing Access and other applications

Their articles always start with general advice before building to comments like your final sentence:
If the above methods will not work for you, it means the data is severely corrupted, then you can try some third-party access repair tools.

My strong suspicion is you are making a thinly disguised attempt to promote that product but are currently unable to post links as a new member.
If that is your intention, you will find your account gets permanently blocked for spamming this site

I reported these posts and the poster to the Admins on the same basis.

 

[Pat Hartman]

A different version of Access is unlikely to do any better at opening the app.

I actually had success with this back when my client was still using 2003. I could take the database home and open it with A2007. Different versions of ACE probably wouldn't have the same effect.