Repair File
The Repair File tool is a maintenance feature that fixes damaged and corrupt files within Working Papers client files. This feature should be performed routinely as a normal maintenance procedure.
How it Works
Repairing files in Working Papers uses the Repair File dialog (Tools | Repair File). The dialog offers various options for repairs and allows you to specify the actions that will be performed during the repair. In the Repair File dialog, you can choose to reindex all databases in the file, renumber all databases in the file, reindex system databases, repost all entries, and recalculate file balances. The purpose of each option is outlined below.
Reindex all databases in this client file
If an index is damaged, you may see error messages or incorrect data in reports that are linked to the damaged index. Reindexing a client file is required if your indices have been corrupt, normally noted when ledgers and journals, reports and working papers display in a random order. Reindexing all databases in the client file fixes these issues. Reindexing also removes records that are marked for deletion, thereby reducing the size of the database files. This may be necessary if:
- Significant editing is carried out in the Report setup, or
- Considerable changes occurred in annotations and commentary text.
Renumber all databases in this client file
If you insert a large number of consecutive records in the same area, insertion may become slower. Renumbering databases in your client file speeds up the insertion of records.
Reindex system databases
Reindexing system databases repairs problems associated with user lists and passwords.
Repost all entries
Performing a repost of all entries reposts all journal entries in the active client file and updates the trial balance. All of the journal entries are posted to the general ledger database and all control accounts in the Report setup are recalculated.
Recalculate file balances
The recalculate file balances options fixes any issues with the calculations in the control accounts and the Statement of Cashflow in the active file.
Other considerations
Best practices for file repairs
According to best practices, files should be repaired in the following situations:
- Prior to performing a year-end close.
- When an error message appears such as Code base Error -070.
- When you have unexpected results such as duplicate lines are showing or lines skipping on an automatic document.
- When your computer or network crashes while you had a client file open.
- Routinely as a normal file maintenance procedure.
