In certain unusual circumstances, it is possible for records in the database to become corrupt. Specifically, editing a test after it has been taken in Tester can cause corruption of the score records for Test Takers who previously took that test.
Database corruption can be identified by running the Update Legacy Data tool. If the Update Legacy Data tool identifies any corrupt records, it creates a file called TGerrors.html in the TG program folder. TGerrors.html contains detailed information about what data is corrupt.
After running the Update Legacy Data tool, corrupt data is visually identified in TG in the following ways:
Reports containing corrupt data may have an alternate icon in the report view tree.
Reports containing corrupt data display a prompt to that effect before opening.
Corrupt data is highlighted within reports.
The word "corrupt" appears before the test taker last name in the Scores folder when highlighting a test in the Tree Directory.
The word "corrupt" appears before the test name in the Scores folder when highlighting a user in the Tree Directory.
Unfortunately, due to the nature of how data records are corrupted, it is not possible to fix corrupt data. If corrupt data is identified in your database, we recommend the following steps:
As always, backup your database before making any major changes to your TG network (running the Compact/Repair Database tool, installing a TGU, etc.).
Backup your database again when you discover data is corrupt.
If you are unsure when the Update Legacy Data tool was last run, run the Update Legacy Data tool again.
View TGerrors.html to see exactly which records are corrupt.
Manually delete the corrupt records listed in TGerrors.html
- OR -
Export only the data you want to keep (tests, users, etc), reinstall TG, and import the data back into TG after reinstalling