Repairing a Damaged File
Introduction
Repair+ is a utility you can use to repair a corrupted RESUMate Database file (RDB). It can also be used to compact a file, which removes unused space and refreshes internal indexes, making overall program operation faster.
While Repair+ is usually successful at repairing a corrupted file, it cannot repair all types of corruption. In these cases it is important to have a recent (preferably nightly) backup. You can view another Knowledge Base article which covers backing up your database here: http://www.resumate.com/tn_backup.asp
Installing Repair+
If you don't already have Repair+ installed (look in Start/Programs/RESUMate for RESUMate Repair+), then you can download a setup program for it from the following link:
http://www.resumate.com/binfiles/repairplus_setup.exe
Download and run this program to install Repair+.
Repair+ Options
Selecting the File to Repair or Compact
» Current database file
By default, Repair+ checks your System Registry to see what RDB file you have opened most recently, and fills that filename into this option. This is the most common action to take.
» Current System File
The System File contains your calendar data. It is opened automatically when the program first starts. If you are experiencing problems with the calendar, or if RESUMate fails to load properly, you should try to repair the System File.
» Other file
In some cases, another RDB file may be corrupt. Use this option to select that file and repair or compact it.
Selecting the Action to Take
» Run full Repair+
This is the default action. Depending on the size of your file, it can take several hours to complete a full Repair+ operation.
» Compact database only
Choose this option to perform a relatively quick database compact. This is the same as running Compact and Repair from the File/Database/Tools menu of RESUMate itself. More information about Compact and Repair can be found at the following Knowledge Base article: http://www.resumate.com/tn_compact.asp
Selecting When to Run the Selected Action
» Run now!
Selecting this and clicking the Begin button starts the selected action immediately.
» Run at scheduled time
Selecting this option and clicking the OK button will cause the selected action to start at the indicated time. This will only cause the program to excute once; for example, you may want to schedule the program to run after hours for the current day only. If you want to run Repair+ automatically on a regular basis (to compact the database, for example), you can use the standard Windows Task Scheduler, and use the Repair+ command line options (see below).
Running Repair+
The file being repaired should not be open in any copy of RESUMate while Repair+ is running. This is true on the local machine, as well as on any machine on your network.
Once the appropriate file is selected and action chosen, click Begin to start the repair process. When finished, you should receive a message stating "Repair+ complete. Would you like to close Repair+?" At this point your file should be repaired.
Your original file will remain untouched, and be renamed with a ".BAK" extension. The repaired file will have the original filename when the operation is complete.
Command Line Options
Repair+ can be run from the Command Line with a variety of options. This is most useful when using a scheduling program, like the Windows Task Scheduler, to run Repair+ automatically.
The command line syntax is as follows:
Repair+ RDBFile [ /R | /R- | /C ] [ /P:password ]
RDBFile Path and filename of file to be repaired or compacted.
/R Perform full Repair+ on RDBFile. This is the default option if no action switch is specified.
/R- Perform full Repair+ on RDBFile, but skip the initial Basic Repair step. Depending on the level of database corruption, the Basic Repair can fail, causing the entire Repair+ process to stop. If this happens, use this switch to avoid running the Basic Repair step.
/C Compact RDB File only.
/P: Use the word following the colon as a password for opening a protected file. Note: for this feature to work there can be no spaces in the password itself, and the password should immediately follow the colon (there should be no space between the colon and the password).