Once you issue the TableUpdate, the data is actually written. Hence when you look at it in the other form, it is up to date.

Enabling buffering doesn't mean that you freeze the table at a particular state, just that the changes made INSIDE that datasession are not written until you commit them.

Actually, you have the OLDVAL() and CURVAL() functions to look at the field values as it where when you enabled buffering, or as currently read from disk (not from you buffer).

I hope that clarifies the point.


> I have set my forms' to 2 -private datasession. And, I have a simple test with 2 instance of my form.
> Both instance of form will USE table and set it to table buffering mode in INIT.
>
>USE mytable AGAIN SHARED
>CURSORSETPRO("buffering", 5)
>
> I update a particular record in 1st instance, and issue TABLEUPDATE(). It return .T. to me. Then, I goto 2nd instance to lookup the same record, it will give me the MOST updated record.
> Does VFP only fetch the data once it is needed even buffering is set?