Sorry, I do not know.
I got missing records when I moved to VFP6 and since that I always include audit in the maintenance application to check for actual number of records and to rewrite the header.

>>>>>>>>>>>>>>>> previous messages >>>>>>>>>>>>>>>>>>>>

It is that the number of records in the header is less than the actual. What matters so far as the Service Packs, is it the DLL files or which version of VFP was used to build the .EXE?

Thanks

Brenda


>I do not know why, but if the number of records in the header is less than the >actual number of records in the table, then VFP6 just ignores records above >the scope (at least SP1, SP2, SP3).
>Previous versions of FoxPro were sensitive for this. May be the new version >has the same ability as the versions before yours previous.
>
>Yuri

>>>>>>>>>>>>>>previous messages below>>>>>>>>>>>>>>
>>I installed new software at 24 sites today. 3 sites have called about problems with a corrupted Codes free table (VFP 6). I do not know if the other sites do not have the problem are have not had it yet. I did a backup before the conversion program and the backup Codes table is OK. The conversion program did not open or change the Codes table. They copy the backup Codes to the current Codes and everything is OK for awhile but then Codes gets corrupted again. I have not found a pattern as to when the Codes table becomes corrupted. But what I can be looking for?
>>
>>I did add FLUSH statements to all update logic. Could that be a problem?
>>
>>Brenda


>I've never seen FLUSH cause a problem. What other changes were included in >this new version?

>Why and when would the CODES table be changed by the program?

>What is the nature of the corruption?

I feel a little better. Did a restore and the Codes table and it was corrupted even before my conversion. It is just a mystery as to why the old software did not give any error messages and and new software give the Corrupted Header message. The error routine has not changed and the use of the Codes table has not chnages.

Brenda