>>Even though I use integer surrogate keys a lot I don't put integer field as the first field. If I can't find any other char field I place a dummy char field as the first field. Using integer field as first one caused me enough headaches in the past (as per corruption).
>>Cetin
>
>Hi Cetin,
>
>Just curious, which versions of VFP did you have trouble with corruption using integer as first field and has this "bug" been fixed in later versions? I am using VFP 6 SP5 accessed via odbc, with structures as noted, and I have yet to observe data corruption. I just wanted to get a heads up before I run into this problem.
>
>TIA

Elmer,
I can't say. As I said I can't even demonstrate it. In that case doing so might be a coincidental cure (maybe something else I did prevented it or was a change in HW/net). Since I'm happy not having it I didn't try to check with which versions it does and doesn't (how would I know w/o a test on hand). Without having a reproducing way I don't call it as a 'bug' :)
Cetin