>>What general rules/situations does one have to consider before selecting Row Buffering vs Table Buffering. Are there any guidelines for picking Row Buffering vs Table Buffering?
>>
>>Thanks
>
>Hi John,
>Despite the attractiveness of row buffering, a downside is that if the record pointer moves for any reason, changes are committed to the underlying table *without* tableupdate() being called. Hence table buffering is recommended by many in most circumstances (which unfortunately is not the default).

Is TableUpdate() called in code or called automaticly when using table buffering? What is the downside of TableUpdate() not being called?

Thanks