As it's name implies row buffering one cursor record at one time. As soon as the record pointer moves, an implicit TABLEUPDATE is performed. This can be a problem if you don't control the TABLEUPDATE, because if it's unsuccessful, the user will get a message to revert the record, which isn't too friendly.
Row buffering is usually used on the parent cursor. However, one school of thought says to use Table Buffering instead and TableUpdate on a row by row basis if necessary. (Thanks to Effective Techniques for this idea.)
Contributors: Nancy Folsom
Category Data Buffering
( Topic last updated: 1999.12.05 11:59:55 AM )