Compact & Repair

Compact & Repair is a basic maintenance utility that is built into every version of RESUMate.  Running Compact & Repair both reduces the size of your database and calendar files (by removing unused space) and can repair minor problems with the database before you even notice them.

NOTE: If you have a multi-user version of RESUMate, make sure that all other users have RESUMate closed before you start Compact & Repair.  Only the person running Compact & Repair can have RESUMate open during the operation.

Step 1 – Click the File menu in RESUMate and select Database | Tools | Compact & Repair.  (It’s all the way at the bottom.)  This will open the Compact & Repair window.

CompactRepair

Step 2 – Make sure that “Current Database File” is selected and click the “Compact” button.  You will see this message:

CompactRepairRunning

Depending on the size of the database file and how long it’s been since the last time the utility was used, Compact & Repair may take just a few seconds or it may take a few minutes.  Let it run to completion.  You can use your PC for other tasks, but you will not be able to use RESUMate.  Once Compact & Repair is finished, you will see a message that reads “Compact and Repair is complete.”

NOTE #2: It’s a good idea to run Compact & Repair on the Calendar File as well.  Simply return to the Compact & Repair window (File | Database | Tools | Compact & Repair) and select “Current Calendar File” in place of “Current Database File”.

We recommend that you run Compact & Repair on your database file at least once per month.  If your database contains more than 25,000 records, we recommend that you run Compact & Repair once per week.  Not running Compact & Repair on that schedule probably isn’t going to cause you any problems, but doing so costs no money, takes very little time, and can prevent serious database corruption from developing.

If you find yourself needing to run Compact & Repair more than once per week, you may have a network or other issue that’s repeatedly corrupting the file.  In that case, you should contact technical support with details of the problem.