>>>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?
>>
>>You just hit on the reason I always use table buffering, even when the user can only be editing one record. To save myself from changes accidentally being committed before the user chooses save, by stupidly moving the record pointer in a field's valid or something.
>>
>>Yes, I should be smart enough to USE AGAIN in a valid routine which looks for a duplicate value in the table, does a CALC or COUNT, or for some other reason moves the table's record pointer. But sometimes I'm stupid, and using table buffering protects me from that.
>>
>>The answer is that, if you move off the record and there ISN'T a problem, the changes are saved, and that may not be what you wanted.
>>
>>HTH,
>
>What about of buffer size? It seems to me as strong indication to use row buffering as preferred way (if buffering is used at all).


Now don't go confusing the issue... I had just decided on table buffering. :)

-Michelle