How many records does your view return? I usually like to have a view that reeturns a single record that's used strictly for the record the user is currently modifying. This way I can requery it very quickly. You could also change the view to use Key Fields Only in the update where clause. This would prevent the conflict but it would also prevent VFP from alerting you if someone else changed the data since you last requeried the view.

>Thank you, Josh, I also thought about requery(), but I feel it is a little bit too expensive. Anyway, I am in a hurry and I will just requery() for the time being.
>
>
>>If you REQUERY() the view each time the user saves a record you'll avoid the update conflict.
>>
>>>I have a remote view. A user edits a record in a form and click the save button, so far so good and the record is updated in the SQL Server. The user keeps making changes with the same record and click the save button, now I get update conflict. How do i avoid this conflict? My code dose check for update conflict when a different user update the same record. TIA
>>>
>>>Chen