>VFP 8.0 reports a file as corrupt but vfp 7.0 is fine with it. Has anyone experienced this? It is causing me to have to put back stuff to 7.0 at a very fast rate.
>

Whether it's in VFP7 or VFP8, the table still has a problem that needs to be addressed (invalid record count in the header). However, in VFP7 the problem would usually only show up if the table was being updated inside a transaction (the table wouldn't get updated -- and you'd never know it until you noticed missing records).

I used to fix this problem in VFP7 by following these steps:

USE BadTable EXCLUSIVE
COPY TO TempBadTable
ZAP IN BadTable
APPEND FROM TempTableTable

This would probably also work in VFP8 if you SET TABLEVALIDATE TO 0 before opening the offending table.