Hi Mike,

I think you meant to say record buffering was set at first in the phrase 'At first I set Buffering to Optimistic table' and this explains why the remote view tried to update the data once you moved off the modified record, this is simply the way remote views work with this type of buffering.

To avoid this behaviour as you have already figured out, you use table buffering instead. Normally you would get update conflict when the data you are trying to save has been already changed by another user and in case of you wanting still to force the updates, you use that paramater (.T.) in the update command.

I would mark the primary key as updatable in the remote view and repeat the test to see if the above mentioned holds true or not, it should.