Hi Mark,

Please ignore my last post...I'm sorry to have bugged you...I assumed that my views were using table buffering because I read somewhere in help, at least I thought I did, that if a view was used as a recordsource of a grid that its buffering was set to table buffering if buffering was enabled. Anyway I had buffering enabled and this view is a recordsource of a grid so I just assumed that the buffering was table buffering.

For the heck of it, I went into the property sheet of this view and switched the buffermodeoverride to 5 and my problems, at least with my initial testing, seem to have gone away.....

Thanks for your help and sorry I was so boneheadded on this one.

Paul
>>I have a view where some new records have been added. I then scan through the view and issue a replace on a record that was just added and I get this error message "Update Conflict" when I hit the endscan to move to the next record in the view.
>>
>>How can I avoid this?
>
>Are you using row or table buffering? I have had a similar problem [my own fault] where I added a record to a view with no KeyID [the KeyID is generated when written back to the source table where I have defaulted the KeyId to be GetPrimaryKey("TableName")]. So while I am working with the view, any new records have a KeyID of zero and they still do not exist in the source table. If you use record buffering, you could have triggered an update that wrote the new records to the source table. The source table now has these new records but with a legitimate KeyID. However, the KeyID in the view is still zero. They will remain zero until you requery() which can be bad if you have uncommitted changes.
>
>What is the backend? VFP? Oracle? SQL Server?