Record ID's

PROBLEM

Damaged records with a bad ID number give error messages, and may be difficult to find and delete.

They are not common, but can be caused by an interrupted save. Several users have reported damaged records caused by a bug in the multi-user version which is also fixed in the same version.

Caught By

Turtle Creek testing and several user bug reports.

Workaround

None.

Solution

Goldenseal 3.2 adds much better handling of record ID's. It is now much less likely that the ID number will be damaged.

Technical Details

Goldenseal keeps a separate index of ID numbers for each record, so if the stored ID number does not match it, we now verify the record internally and correct the stored ID.