Hi David, 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).

Agreed. In general, you want to try to use row buffering with parent tables (tables where a form is relegated to showing individual records) and table buffering with child tables. When using optimistic buffering without specification via Form settings, row buffering is the default *except* for tables using a Grid, where table buffering is forced.