>>First of all to the MULTILOCKS question - if this is true I have the same question, however as far as I know, MULTILOCKS has nothing directly to do with buffering at all. If there is a need to lock more than one record at a time then MULTILOCKS must be on. With Table Buffering this need exists, with Row Buffering it doesn't.
>>
>
>My assumption is that buffering is done in an invisible CURSOR. When you edit the field, an implicit lock is placed on the record in the buffer. (CURSOR)
>
>When you tableupdate() a lock is place on the record in the actual table (TWO LOCKS NOW EXIST) so that it can be updated.
>
>BOb

This is true with Optimistic Buffering. Pessimistic Buffering places the lock on the record in the actual table when edited -- before the tableupdate().