I've been getting header corruption on some client sites lately. Most of them seem to be "Incorrect Record Count" mismatch type of stuff. I know that there is a window of opportunity for this to happen because fox writes to the header block first and then updates the records so if there is an interruption they can get mismatched.

My biggest problem is that there isn't an error message generated the next time I try to update the table. I try to write a new record and it is there until I close the transaction and then it magically disappears. Actually it resides in the reccount()+1 record and eof() is .t.

1. Is there a way to generate an error message when this happens.
2. What might be happening to cause the corruption in the first place?
3. Is there any relation to table size? Longer window between header and table write?
4. I can use foxfix to check for it every time I write to the tables, but this seems REALLY kludgy. Any suggestions on a better work around?

Thanks to all.