I had this problem with a client's app this week. They didn't realize that
their backup of the back end didn't include the .mdb file (their network
contractor put it on a dedicated workstation because it was a mission
critical file, but then didn't back it up because it was just a workstation.
sigh.
I went after the file by OKing the attempt to fix - and it did. However, it
went from 15 mb to 5 mb in the process. I checked every table by opening
and jumping to the last record - everything looked good. I ran some of the
summary reports and the numbers looked right.
Any ideas on why so much space was recovered. I compacted MY backup of the
db from the prior week and got very little size reduction.
Any ideas?
Tim Mills-Groninger
<ba**********@yahoo.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com...
Hi, all
We have a database which was running on the server and used by several
users. We can not the database now with the following message:
The "*.mdb" need to be repaired or isn't a database file.
You or another user may have unexpectedly quit Microsoft Access while
the Access database was open.
I tried to compact and repair, but it was failed. I tried to open a new
blank database file and import the bad database file, it was failed
too.
Please give me some suggestions!
Thanks a lot for the help!