I've also been working with MS Access since v1.1 and have seen this same problem where databases get corrupted and then trying to recover as much as possible manually. As far as an answer to the last post, if it is possible at all to open the damaged database, I would recommend creating a brand-new database and attempt to import objects from the OLD database, rather than trying to export to a new database. After being presented with this situation at least 15-20 times or more by now, it frequently seems that it ends up being usually one, maybe a couple, of objects that are actually corrupting the entire database.
During the import process within the new database, those objects that are outright corrupted will be flagged using a message box from Access, and it will usually attempt to continue importing any other objects that you had selected. Worst-case scenario is to import one object or a few objects at a time (which usually is a MAJOR pain), followed by a repair/compact on the new database each time. With that, it may help to do a backup on the new database every few objects or so as an insurance.
Hope that helps at least a little. Not a pretty solution, but I've been successful with it most of the times in the past.
|