I just did a little test and it appears that it just doesn't get saved at all. I haven't looked into it thoroughly, though. I always make sure the code does a TALBEUPDATE() or TABLEREVERT().

>I always force the update because in this case there's rarely a conflict and last one to save should win. If I move off the record and there is a problem, what will happen? Will I get an error? Will it force it? Will it just not save?
>
>Thanks,
>
>-Michelle
>
>>Michelle,
>>
>>Row buffering will attempt to update the data when you leave the record. You still might want to explicitly use TABLEUPDATE() so that you have flexibility over when data is saved. I usually use Row buffering when the user is working with a single record at a time and table buffering when I want the user to be able to modify multiple records between saves.
>>
>>>I've been using table buffering exclusively, and peppering my code with TABLEUPDATE all over the place. For grids, table buffering is obviously good, but I'm wondering if I should be using row buffering in the case where the user is looking at one record at a time.
>>>
>>>Does row buffering automatically save when you leave the record? I thought I heard that it did, but I'm not positive.
>>>
>>>What do you think?
>>>
>>>Thanks,
>>>
>>>-Michelle