Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / New Users / June 2006

Tip: Looking for answers? Try searching our database.

Error message when opening DB

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
gls858 - 21 Jun 2006 17:08 GMT
I get this error message when opening one of my databases:

Microsoft Jet database engine could not find the object MSysDb.
Please make sure the objects exists and that you spell the name
and path name correctly. DB won't open.

Is a restore from backup my only choice or can this be fixed.

gls858
Jerry Whittle - 21 Jun 2006 18:13 GMT
At times like this, nothing beats a good backup. There's a very good chance
that it's toast as it can't find a MSys table.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp
Signature

Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

> I get this error message when opening one of my databases:
>
[quoted text clipped - 5 lines]
>
> gls858
gls858 - 21 Jun 2006 19:19 GMT
> At times like this, nothing beats a good backup. There's a very good chance
> that it's toast as it can't find a MSys table.
[quoted text clipped - 8 lines]
> towards the bottom this page:
> http://www.rogersaccesslibrary.com/OtherLibraries.asp

Thanks Jerry. We have a daily backup of the file just hoping to
save some data that was entered between the backup and the corruption.
Ended up restoring the file. Not a great loss of data but still time
consuming to track down what was entered after the backup.

gls858
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.