• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2008
  • Last Modified:

MS Access 2003- The Microsoft Jet database engine could not find the object 'MSysDb'.

Serious Problem:

Our Access 2003 database, for reasons very much so unknown to me, is reporting the error:

"The Microsoft Jet database engine could not find the object 'filename'. Make sure the object exists and that you spell its name and the path name correctly."

I do have backups of the database available, but it changes significantly day-to-day, and that information needs to be recovered.  I've tried several recommended solutions, compact and repair, MSQuery, JetComp, and several different attempts to access the records and simply import those into the database backup, with no luck.  

Thank you very much for your help.  Any suggestions are appreciated.  
0
mrables
Asked:
mrables
  • 4
  • 4
1 Solution
 
jmoss111Commented:
Hello mrables,

Have you tried opening an empty db and importing all the objects one by one and checking that you can open the imported ones before continuing to the next object?



Regards,

Jim
0
 
mrablesAuthor Commented:
I have tried the database recovery tools and, while they work, I cannot spend the money to purchase them.  How would I go about importing the objects one by one?  I have tried opening a blank database and importing the broken one, but it failed with the same message.

Thank you very much.

-Mr. Ables
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jmoss111Commented:
Do the import just like you did except do it for one object at a time, check to see if you can open and then continue to next object.

Are all your objects in one db, IE data tables, queries, forms, reports, etc?
0
 
mrablesAuthor Commented:
Correct, all of the objects are in one database, that cannot be opened.
0
 
mrablesAuthor Commented:
It seems that the data in the table is more corrupted than I had assumed.

The files from the day that I need are completely missing, along with about 1/3 of the rest of the data.  I cannot seem to find any reason for this either, the logs tell me nothing.  While it is alarming, we can redo the data from the missing day and input it into the backup from the day after.  If that backup was not available, there would be huge problems.

Moral of the story for anyone who works in the IT field (and I think anyone who has any experience in the field knows this very well): always backup your important data.  If it is updated daily, it should be backed up daily.

Thank you jmoss111 for your assistance.
0
 
mrablesAuthor Commented:
The data in the DATABASE, I meant, not the "table".
0
 
jmoss111Commented:
You can either live or die by backups; i've been in IT for well over 30 years and got my discipline in highly structured belt, suspenders, and a rope around the belt mentality datacenters.

You're welcome; glad that I could assist.

Jim
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now