I usually don’t recommend starting with a rebuild, but with Tools > Restore Backup in cases of database corruption.
If you have already tried Restore Backup on the most recent internal Backup folder without success, try this:
Make a copy of the database and let’s work with that copy.
With the database open (I assume you can open it), choose Tools Restore Backup and select the next most recent internal backup folder, Backup0. This is a reversible operation. The current contents of the database are swapped with the contents of Backup0. If the database had not been corrupted at that time, you should recover a working database, although you will have lost more recently entered material.
If you cannot open the database at all, it’s still possible to recover from an internal backup folder plus the internal files folder.
Create a new folder in the Finder – call it Harry for the time being. In the Finder, choose your database file, click on the Actions button and choose the option to show package contents.
Open the folder named Backup, select all of its contents and copy (Option-drag) the files into the folder named Harry. Also copy the folder named Files into Harry. Note: If the contents of Backup were corrupt, repeat this part of the procedure using the contents of Backup0 (and if still a problem, use the contents of Backup1).
Harry now holds the contents of one of your internal backup folders, plus a folder named Files. To turn it onto a DT Pro database, select (don’t open) Harry and press Command-I to open the Info panel. Change the name of this folder as appropriate, adding the suffix “.dtBase” (without the quotes, but case is important). Press Return and close the Info panel. Now you have a DT Pro database package file.
Double click on the database file to open it under DT Pro. Fingers crossed, you have recovered the material you were seeking.
Recommendation: I like and use DT Pro’s Scripts > Export > Backup Archive. After making significant changes to a database, when ready to take a break it only takes seconds to invoke the Backup Archive routine. On return from break the database has been verified, optimized and has current internal and external backups. For added safety (a hard drive could fail, my laptop could the stolen or whatever) that compressed and dated archive file can be copied to an external device – a CD, DVD, portable drive or another computer.
Although I think backing up is prudent and I do it, I haven’t had to resort to a backup in more than two years. My databases are very stable. My operating system is pretty much as Apple designed it. I rarely install applications (such as haxies) or plugins that deliberately modify the operating system, as we often see problems resulting from installation of poorly written code, especially after OS or Security updates from Apple (run the Disk Utility permissions repair routine before and after such updates). And I do routine preventive maintenance on the operating system and disk directory. Utilities such as OnyX or Cocktail, and a directory ‘fixer’ like DiskWarrior 4 can keep your computer running cleanly and efficiently and will nip small problems in the bud before they cause big problems.
Try to think about what could have caused your database problem, such as a system crash, a power outage, recent installation of new applications or utilities, etc. And backup.