>>
>>If a form using the default datasession contains a table that is already opened, another copy IS NOT opened. The form uses the copy that is already there. If the cursor in the form's DE is set to use a different buffering setting than the table already opened, the form changes the already opened table's buffermode to suit its needs. The form will NOT close the table if it did not open it, but is also not polite enough to change the buffermode back to the way it found it.
>
>Actually, I've found that the form does not change the buffering. The table was opened for Opt Table Buffering and the form was set for "no buffering" (0 - Default). My trap showed that the table in question was still buffered during form execution! BTW BufferModeOverride=1 (use form setting).

Ok you're right. And so am I. It looks like the form will turn it on if it needs it, but will not turn it off if the table is buffered, and it's own table in the DE is not. IOW, try the test the other way around, and you'll find that the form does indeed change the buffering. Interesting.