>> The bug seems to appear when the position of the field int1
>> doesn't correspond to its natural position, but the bug is into the logic > of the C++ code.
>> For an INT field VFP uses the format of the field(copyOrder):
>
>Fascinating. That explains it, and I can reproduce it and, I suppose, code around it. I wonder what other types besides INT revert to this physical field order anomoly?
>

Yes.
This bug is born when the VFP Team added the Integer datatype.
In the same instant it added another datatype : currency
Of course, this bug it also torments the type currency!

>Franz