>Hi Peter,
>
>I wrestled with these issues late last year, and by chance I came across Gareth's KB article which reported the 'problem' that if records were added to a corrupted file (header count error), no error was reported. It is now classified as a 'bug'.
>
>You might verify this in your situation, simply by corrupting one of the tables known to have the problem. I did this with a journal file which adds a record for every transaction event. With the table corrupted, the program apears to run normally, but no journals are added.
>
>The only workaround, I think, is to add the new record with only its primary key, make sure it is flushed to disk (not necessarily with flush) and read it back to update the rest of the data.

There was another workaround, which helped in those cases when
- user A creates a new record
- user B creates a new record
- user B saves
- user A saves and overwrites B's record
The workaround was to call Reccount() immediately after the tableupdate(), which somehow forced the header to be updated with the correct record count. May as well work in other cases.