>Hi Luzt:
>
>> I would not use timestamp, since there is nothing to sync the times of two computers
>
>You are wrong on this, the timestamp have nothing to do with synching, but only to know "which record is newer". In a normal scenario, this field is correctly updated, but can happen (I saw this) that two or more records have the same timestamp, then you can't know which one is newer, and in this case you must use the 2nd.way of resolution I've mentioned in another post.
>
>Physical position of the record can't be used too, because that's what a situation of corruption code or data means, you can't assume "a logical" way of behavior.

Fernando,

what I mean is like Message#1636750 where the OP clearly states that

-the problem was old but working for VFP
-VFP used the last record(set) for a while
-Foxbin2Prg used the first record(set)