Getting RTE 7010 but rebuilding indexes doesn't fix the prob

[Gavin Walker]

Also, if you do a pack data you get error 7010 on various tables including Office Hours tables and the transaction table.

Not only does error 7010 indicate a corrupt index file, but it can also indicate a corrupt memo file (*.adm). In one particular case I know of an end user decided to clean up their data files by deleting all the .adm files. This made Medisoft inaccessible. Unfortunately, they did not have a backup of their data.

The data was corrected by writing SQL scripts that removed all references to memos in the database and then doing a pack data and rebuild indexes.

Needless to say, all of the customer's memos were lost. This included appointment notes, case notes, transaction notes, claim notes, and anything stored on the multimedia tab on the case.