Actually I am getting the error without the second tableupdate. I was hoping to solve it by adding the second command on the other alias.

>The answer to your question is NO.
>
>The conflict could be that the second tableupdate() is trying to update a record that's changed between when it was edited and now.
>
>Lookup tableupdate() there are other options you have to trap the error or ignore chnages made elsewhere.
>
>Regards
>
>Mathias
>
>>If a table is open twice using 2 different aliases, and buffering is 3 for both instances, and an edit is made followed by:
>>
>>=tableupdate(,.t.,"alias1")
>>
>>should this be followed by
>>
>>=tableupdate(,.t.,"alias2")?
>>
>>I am getting a error that says there is an update conflict error in alias2.
>>
>>I'm still a little confused by this buffering business.
>>
>>Thanks