I suppose if I'm always doing TABLEUPDATE anyway, I guess I might as well stick with table buffering since I won't gain anything with row buffering.

Thanks,

-Michelle


>With record buffering on, if the record pointer leave the record, VFP will try to save the change automatically. If it fail, the user will see an error message (yuck!).
>
>To reduce the chance that some obscur method hiden deep in a class change the record pointer as a side effect and because table buffering doesn't cost more than record buffering, I allways use table buffering.
>
>The only downside of table buffering is that you cannot create an index with table buffering on. In that case, I change it to record buffering, create the index and put back table buffering.
>
>HTH
>
>>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?