Im still using VFP 6.0, but the corruption detection feature in VFP 8.0 sounds like quite a time saver when it comes to locating corruptions. I had no clue what was wrong with the table until I posted and received your responses. No error messages, even though it was corrupted. *By the way, the problem was exactly how you and Neil described it. I should have posted here from the start.

Since I'm still using 6.0 for now, do you know of any documents/articles which describe the various types of table corruptions and how to fix them?

Thanks for your help,
Dave

>I think Neil is on the mark here. Note that VFP8 will detect this type of corruption when you USE a table or add records to a table in such a state. Either adding a record, deleting it then packing the table, or adding a column then removing it should fix the problem if it is indeed a header record count / physical file length mismatch issue.