Database Corruption: It think it has been partially converted. HELP

For some reason, which I may guess at in a moment, is giving me an error message when I attempt to open it: "The database is an unexpected state.  Microsoft Access can't open it."  The message goes on to say that the database was converted from a prior database by using a "DAO CompactDatabase" instead of the Convert Dabase command and that it has been left in a partially converted state.

I can not open the database whatsoever and I did not attempt to convert the database.  However, my network directory size limit was reached while I was working on the database.  I may have attempted to compact the database with the directory max'ed out, but not sure.  I also had my PC on its knees with several programs running including Lotus Notes and several ArcMap projects all at the same time, so I'm sure my computers memory resources were at a minimum.  

Is there a way to recover my database or am I forced to go to a backup copy and lose several days work?
TetsingerAsked:
Who is Participating?
 
jadedataMS Access Systems CreatorCommented:
it may be time to start talking about what backups you had
0
 
jadedataMS Access Systems CreatorCommented:
Greetings Tetsinger!

  Try opening a new empty database and importing all objects into it.
  Make sure you're joined to your database system workgroup (mdw) for this when making the new mdb

regards
jack
0
 
TetsingerAuthor Commented:
How can I import objects into a new database when I can not access my damaged database?  How can I access the damaged database?  I attempted to use the menu command, Get External Data ->> Import, from an empty database, but I got the same error message.
 
Tet
0
 
TetsingerAuthor Commented:
Thanks for your help.  I figured that was my only option.  Just wanted to make sure I was not missing a possible solution.  

Do you have any idea why this has happened??

Tet
0
 
jadedataMS Access Systems CreatorCommented:
same as with any network interruption.  when the file convertion was interrupted by the loss of disk space the operation abended.  bad. always bad.

be VERY aware of how much disk space your application will need as it grows.  a rule of thumb is that you need four times the size of the database on the disk that the db sits on to do a compact.
any less than that and you are risking getting corrupted or at least interrupted.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.