RESUMate’s built in 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:

1.  RESUMate itself is closed on your PC and any other PCs on your network.
2.  See #1.  Repair+ cannot run successfully while anyone is using RESUMate.

Repair+ Install File

If Repair+ is not installed on your PC, or if you are using a version lower than 15.0.1, you can download the install file here:

Repair+ Utility  (v. 15.0.1)

Repair15Unlike Compact & Repair, which is built into RESUMate itself, Repair+ is a separate program.  If you are using RESUMate 12 or higher, Repair+ is probably already installed on your PC, all you have to do is open it:

– On Windows Vista, Windows 7, and Windows 8.1, click your Windows Start button and type “Repair+” into the search bar.

– On Windows 8, open the “Charms” menu (the icons that slide out from the right side of the screen) and search for “Repair+”.

In the “File to Repair or Compact” 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 Other File” button.  Once the file to be repaired has been selected, blick the “Begin” button and Repair+ will start.

Repair+ can take anywhere from a minute to several hours 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.  While Repair+ is running, you can continue to use your computer, but do not open RESUMate or shut down the PC.

RepairCompleteOnce Repair+ is finished, you will see the message at right.

Click “Yes” to close Repair+.  You and everyone else on your network can now open and use RESUMate normally.

Note#1: 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.

If Repair+ does not run successfully:

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 “Run full Repair+, skipping 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.