Access db nuked after compact?

[Feuerstein]

Hey all,



I was just working on my database and decided to compact/repair it. I got this weird message:

Microsoft Office Access can't delete database xxx after compacting it. The compacted database has been named Database.mdb.
If you compact a database using the same name, Microsoft Access creates a new compacted database and then deletes the original database. In this case, however, the original database wasn't deleted because it is read-only.
If you can, remove the read-only status, delete the original database, and then rename the new database using the original name.
If you can't remove the read-only status, inform your workgroup administrator.

So I clicked ok and got a "Could not find file" message. Indeed, it is gone.

Did I just lose several weeks worth of data? Is that a feature? Is there a solution to salvage the data, or is it just gone?

[June7]

I have encountered this before. Fortunately my db is split and no data lost but had to revert to a previous version of the frontend and redo edits. Always make a copy before doing edits.

[Feuerstein]

Thanks. Wow. What a giant POS software.

[Access_Blaster]

Thanks. Wow. What a giant POS software.

This Hotfix is suppose to address this problem.

http://support.microsoft.com/?kbid=950812

Do you have all your updates?

[Feuerstein]

Yes, that hotfix is from April 2008 (4 years ago), so apparently it wasn't so hot. I am up to date with patches and band aids for MS/Office/etc.

In any case, good news! This morning I went through my many Access databases to back them up just in case they self destruct randomly, and guess what I found. One called inconspicuously "Database.mdb". Guess what my trust is partially restored.