>>>I noticed that the update criteria in the view designer defaults to "Key field and modified fields".
>>>
>>
>>The question is really a matter of how to handle update conflicts. If modified fields are included in the WHERE clause, the new record will not overwrite the old one because the old one won't be found. If just the PK is used, the last record always wins.
>
>Interesting. However, I thought that VFP would automatically compare old with new values. Does this not apply to views?
>
>Hilmar.

VFP will compare old with new values depending on the buffering setting. When a view uses changed fields in the WHERE clause, it will use the OLDVAL() function to build the SQL statement it uses internally when the view performs its updates.