>>>>>Hank, did you try to change the buffering setting in the Tools/Options/Data
>>>>> to Optimistic (Record) ?
>>>>
>>>>I did this and it would let me change the field data and when I moved to a new record it would NOT give the error. But when I closed the browse window and reopened it, the field data was at the original value and not changed.
>>>>
>>>
>>>This is better. :)
>>>
>>>Try to issuel from the Command Window
>>>llResult = TABLEUPDATE(1, .t.)
>>>and see what is returned in llResult.
>>>
>>>Nick
>>
>>It returns .T.
>>
>>What I described above (previously) works for the remote view that I have saved from an earlier session. But if I try to create a new remote view, I continue to get the error every time I try to exit a changed record!? Occasionally when I open the remote view for the first time and edit a record, it will give me the message that " is busy", or something like that, leading me to believe that it is attempting to write changes. After a getting the message a few times, it will allow me to move off the changed record. It will actually take that change (in the browse window anyway) and any subsequent change gives me the error. When I close the browse, all records are back at the initial settings.
>
>If it returns .T. and SendUpdates is .T. the problem seems to be in ODBC and/or back end.

Also if the Key field is not specified properly, the TABLEUPDATE will return .t., but the changes go nowhere, because it can't identify the record to write to.