>Ed et all,
>
>These statements are incorrect. With Row Buffering only the current record is buffered. With Table Buffering the entire table is buffered. On top of this there is another "buffer" (for lack of a better term) of changes for both buffering types. This is what makes functions like GETNEXTMODIFIED(), CURVAL(), OLDVAL, etc. work.
>
>Also, to be devils advocate, nobody's mentioned the use of views and p-views (my favorite approach) instead of buffering the actual tables.
>
>Cheers

Colin,

Unless you have spoken to the developers at MS then your assertion is flawed. We have no idea from the docs what VFP buffers. We know that row buffering allows one dirty record at a time and that table buffering allows multiple dirty records. We know that row buffering will do an implicit tableupdate if the record pointer moves off a dirty record and that table buffering does not. That is all we know.

BTW, if row buffering does not buffer more thna one record, why does it require multilocks to be ON?