[BCB:18:Wizard code:ECB]
NOTE: If the message 'Check Data Files was aborted' appears, please refer to this guide > Run check data within Demo Data
- File > Open > Open Demo Data > enter Manager in the Logon box > OK.
- File > Maintenance > Check Data.
If the issue also occurs in Demo Data you must first check and remove any old report files.
- Browse to the following directories:
| Sage Accounts v29 | C:\ProgramData\Sage\Accounts\2023\Company.000\Reports |
| Sage Accounts v28 | C:\ProgramData\Sage\Accounts\2022\Company.000\Reports |
| Sage Accounts v27 | C:\ProgramData\Sage\Accounts\2021\Company.000\Reports |
| Sage Accounts v26 | C:\ProgramData\Sage\Accounts\2020\Company.000\Reports |
| Sage Accounts v25 | C:\ProgramData\Sage\Accounts\2019\Company.000\Reports |
| Sage Accounts v24 | C:\ProgramData\Sage\Accounts\2018\Company.000\Reports |
| Sage Accounts v23 | C:\ProgramData\Sage\Accounts\2017\Company.000\Reports |
| Sage Accounts v22 | C:\ProgramData\Sage\Accounts\2016\Company.000\Reports |
- Select COMMENTS.RPT, ERRORS.RPT and WARNINGS.RPT > right-click > Delete.
If the issue still occurs in Demo Data you must uninstall and reinstall the Sage Accounts software.
If check data completes in demo data, click Next.
Nextnull;null;wiz2,wiz1
Check the data on the PC which holds the data and ensure you allow check data enough time to run
If this is not possible, you can move the data on to one of the client PC's and attempt the check data routine again.
To move the data to a client PC null;null;local,wiz2If check data runs fine this shows it is something on the Network which is causing the software to hang or crash on check data. For information about troubleshooting network performance issues please refer to this guide >
Even slow movement of the progress bar means Check Data is still working. Check Data takes longer in areas with large amounts of data. For example, it is not uncommon for Check Data to appear to have hung when checking Bank Accounts. You should run Check Data for at least twice as long as it usually takes to complete before you click Next.
If the issue still occurs, click Next.
Backnull;null;wiz1,wiz2 Nextnull;null;wiz3,wiz2Reindex and Compress the relevant module and clear the audit trail to 01/01/1980
NOTE: Before making any changes to the data ensure you take a backup of the data files. For more information about how to backup your data, please refer to this guide. >
Make a note of the area being checked when Sage Accounts hangs or crashes. The following table advises which areas to ReIndex and Compress:
Before running the reindex and compress routine, make a note of the number of splits. This equates to the number of lines of transaction information in the data. To do this:
- Help > About > Data Information > note the number of splits
After the reindex and compress routine, check the number of splits again, if the number has changed, the data has not been fixed and you should either restore an error free backup or arrange for the data to be repaired at Sage. For more information about sending your data in for repair, please contact Sage technical support.
| Area in which check data hangs or crashes | Areas to ReIndex | Areas to Compress |
Transaction Link Integrity
Ledger Transaction Links
Customer Accounts
Supplier Accounts
Nominal Accounts
Bank Accounts | Audit Trail
Customer Accounts
Nominal / Bank Accounts
Supplier Accounts | Audit Trail
Sales Ledger
Purchase Ledger
Nominal Ledger
Bank Accounts |
| Stock Records | Stock Records | Products |
| Invoice Records | Invoices | Invoices |
| Price Lists | Price Lists | Price Lists |
| SOP Records | Sales Orders
Goods Despatched Notes | Sales Orders
Goods Despatched Notes |
| POP Records | Purchase Orders
Goods received Notes | Purchase Orders
Goods received Notes |
| Good Received Notes | Purchase Orders
Goods received Notes | Purchase Orders
Goods received Notes |
| Project Records | Project Records
Project Transactions | Project Ledger |
To ReIndex and compress the data and clear the audit trail to 01/01/1980
- File > Maintenance > Reindex data files.
- Select the relevant files to reindex using the table above > OK > when the confirmation message appears, click Yes.
- Compress Now > clear the Compress All Data Files check box > select the relevant files to compress using the table above.
- Compress > OK > Close > Close.
- Tools > Period End > Clear Audit Trail > Next.
- Enter 01/01/1980 > Next > Next > Exit.
If the issue still occurs or the ReIndex and Compress option hangs this indicates the data is corrupt. We recommend that you restore a backup of your data prior to the issue occurring. For more information about how to restore your data, please refer to this guide >
As a last resort you can send your data in to us to be fixed. When we repair data it may involve removing a number of transactions however, we may not be able to provide details of the removed transactions. You must also stop processing for the duration of the repair. If you restore a backup it may result in less time to reprocess the transactions compared to sending the data in.
For more information about sending your data in for repair, please contact Sage technical support.
Backnull;null;wiz3,wiz4 Restartnull;null;wiz1,wiz4
TIP: