>>>>Thank you. The goal was not just to have a unique value (what Sergey suggested would have done it). But the goal was to preserve all the existing values and only change the value in records where duplicate exists.
>>>
>>>That's exactly what my script does, if you noticed. I only update fields which are duplicates. The having clause should be > 1, not > 0 (typo).
>>
>>I am curious, as I try to understand your syntax and learn how UPDATE works. It seem like VFP, when executing UPDATE, processes all records at once and then actually
updates the values. Otherwise, in the case of two records with the same value, only one would be set to a new value. That is, when the first instance of the duplicate record is set to a new value, subsequent sub-query would not found duplicate records. Do I understand this correctly?
>
>Update in VFP, as well as in SQL Server, processes all records at once.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
