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


The busy condition you are experience may be related to the advanced option of Number of records to fetch at one time. Set this to ALL or -1 (when in view designer under query, advanced options)

Tableupdate will return .t. even though no data was updated if send sql updates checkbox on the Update Criteria tab is not selected. If your key field is system generated (within the database) it should not be updateable (as you have it). If it is a field you can add then it should be updateable. Also, your updates should be SQL update, not SQL DELETE and Insert. If your key field is updateable, then the Delete and Insert will work, but if it is not updateable, then the delete will work but the insert won't have that field to use to add the record.

Recap:

[1] Number of records to fetch at one time = ALL
[2] Send SQL Updates = True
[3] SQL Where clause includes = Key fields only (better performance, ignore conflicts)
[4] Update Using = SQL Updates