>>There's no way to tell how much data were lost based on the message itself. It could be a few newly added records or all of them.
>>VFP stores the address of the next available block in FPT in the header of the file. Basically it's the same as the size of FPT and they always should much for valid FPT. If they don't than FPT is corrupted. It can fixed either by correcting Next Available block in the header to match FPT size or other way around.
>>
>
>Thank you for the explanation. Good thing for me is that none of the critical tables of the application got hit by this corruption. In fact, I see on the list of tables those that they (customer) don't even use at all. That is, the tables have 0 records and yet the FPT got corrupted. Go figure.

I've seen similar corruption cases. Couldn't figure out why unused and empty tables got corrupted.