Icon View Incident Report

Serious Serious
Reported By: Clive Bennett
Reported On: 6/1/2004
For: Version 4.07 Build 1
# 1744 Updating a Table Can Cause the Checksums To Be Calculated Improperly

I have an internal process to check for and repair data corruption and optimise tables. Its reporting corruption all the time now with V4.07, I cant remember it ever reporting corruption in v4.04. The tables dont actually appear to be corrupted.

I did read the README file that came with 4.07 about the checksums. But even though I have already run a repair, it still keeps on reporting corruption (not straight away) after using my app for a bit.

Comments Comments
The setting of the field data was allowing for possible random bytes past the NUL terminator in string fields, thus making it possible for the calcuation of the record hash to result in a different value at different times.

Resolution Resolution
Fixed Problem on 6/6/2004 in version 4.08 build 1