Issue

In Sage Pro ERP with a FoxPro backend, sometimes transactions do not appear to be written to tables. Why is that and what can they do to resolve this?

Sometimes FoxPro Tables can become corrupted, possibly due to a crash. This may not be apparent while entering the transaction but you may find the transactions missing later. The transactions are most likely in the table but cannot be seen by the corrupted header record. In most case these can be recovered.

Solutions

There is a built in function in Sage Pro System Manager to check for this corruption. This is only available in a FoxPro install.

• System Manager – Transaction – System Recovery – Check table integrity
• On the option grid I would recommend choosing no to Fix Table and get the report

What this tool does and does not do

The tool will check all tables within your grid selection. It will first report on the existing record count. It will then attempt to append a new record to the table and then check the record count again. If the record count has not changed it will report the table as corrupted.

If you choose to fix the table it will create a new matching table structure, copy all records from the damaged table into the new structure and then replace the existing damaged table. This will allow new records to be added to the table but in process the damaged records are not copied over and will be permanently lost. Manual data repair will most likely be needed to resolve any problems related to the missing records. A more complete solution would be purchasing a 3rd party utility such as FoxFix which can completely repair the damaged table without losing the missing records. SQL installs are known to be more stable and this type of damaged has not been reported.

© Copyright Sage Software