>>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.
>>
>>Any comments appreciated
>
>I think it's the VFP7 that should be your worry because it stopped erroring when a header's record count was wrong. NOT one of the brighter moves in my opinion!
>
>So it's possible that your table has been bad for some time. How d'ya like that???
>
>Have a look at VFP8's SET TABLEVALIDATE. Seems you could remedy the situation by setting it to 0, running a PACK, then going back to default setting.

Jim,

PACK wouldn't help if there are no deleted records in the table.