RESUMate's Compact & Repair utility can correct most database issues. However, if you are having a problem that Compact & Repair cannot fix, then it's time to run Repair+. Before you run Repair+, please make sure that RESUMate itself is closed on your PC and any other PCs on your network. Repair+ cannot run successfully while anyone is using RESUMate.
Unlike Compact & Repair, which is built into RESUMate itself, Repair+ is a separate program. Click your Windows start button or type the word "Repair" into your Windows search bar and you should see "RESUMate Repair+" as an app.
In the "Select File" section, your main .rdb database file should be automatically selected as the "Current Database" file. If it isn't, you can select your database file manually by clicking the "Select Specific File" button. Once the file to be repaired has been selected, click the "Begin" button and Repair+ will start. Repair+ can also be used on the RESUMate calendar file by following the directions above but selecting "Current Calendar" file or browsing for a different calendar file ("reswin.dat") with the "Other file" option.
Repair+ can take anywhere from a minute to over an hour to run. The time depends on the size of your database file, how long it's been since Repair+ (or Compact & Repair) was last run, and the speed of your PC.
Once Repair+ is finished, you will see this message:
Click "Yes" to close Repair+. You and everyone else on your network can now open and use RESUMate normally.
The most common reason for Repair+ not to complete successfully is that the database file is locked by Windows. This may be because someone has RESUMate open, RESUMate failed to shut down properly, or simply because Windows is messing up.
If this is the case, Repair+ will typically run all the way to the end before producing either a message that reads either "Path/File access error (Error Number: 75)" OR "Unable to rename temporary working copy". If you see either of those messages, the simplest thing to do is restart the PC where the database file is stored and run Repair+ again.
If Repair+ fails for any other reason, you can try re-running Repair+ but selecting the "Skip initial basic repair" option instead of the "Run full Repair+" option.
If you cannot run Repair+ successfully with either of the above options, you may need to restore a backup copy of your database file.