Hi, Josh

I woudl say that about 80% of my remote views return only a single record. The other 20% may return mostly a few records, or sometimes over 100. I worried about the later case. My save() method is in a form class which all data forms
based on. I use row buffering. All my views use TimeStamp in the Update Where clause. I think I will just follow your suggestion to requery() after save. I just tried, in the worst case when the view returns about 140 records, it only took about 1 second to requery().


>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.
>>