John,

The way that I read that message, simply adding the 2 dummy fields at the beginning is what is required - no other changes to TAG definitions or anything else.

You should, though, do it to all tables having an INT key (at the beginning?).

The balance of that thread described that records get dropped when using TRANSACTIONs. I believe that VFP8 has been revised to cause a FAILURE when that condition is detected. At this time (VFP6/VFP7) I believe that the condition may NOT cause a failure.

IN addition to making dummy fields as noted, I think you might REALLY learn something valuable if you can have the number of workstations restricted to, say, 5 for a good period of time. Peer-to-peer seems to be fine (as someone else has noted) with 5 or less workstations, but can have unknown (at least never fully described here) results as the user count approaches its (alleged) limit of 10. Steve Gibson has described how ANYTHING that happens to be shared, even if only temporarily, is INCLUDED in that limit.

good luck

>Hi
>I have read message #583143 and other relavent thread. I would like to clarify that:
>
>

>Does it meant, adding
>field1   C(10)
>field2   I
>fieldPrimary
>

>
>before fieldprimary able to solve the problem of primary key corruption?
>Also, If my primarykey is a composite key which combine 2 or more fields, do I need to add 2 dummy fields too?
>Ex.
>FieldA
>FieldB
>FIeldC
>
>Index Expr:
>PrimaryKey FieldB+FieldC
>
>Or I should have a additional field that is combination of FieldB and C?
>
>Thank you