Jim,

>First buffering is not what Walter has stated exactly. Buffering has always been part of Fox. The proof is that in Fox 2.x when editing fields directly the disk light did not flash with every keystroke of the user. That means that Fox was buffering the user's work and would write it to disk later. The problem was that we had no control over when or if that buffer would be written, it would and whenever fox was ready to do it.


Buffering in Fox 2.x was much different than in VFP.

Buffering in Fox 2.x was build up in two layers:
- The data on disk
- The data in the OS local buffer

In VFP, it is build up out of three layers:
- The data on disk
- The data in the OS local buffer
- The data in VFP local buffer for record or table buffering

The third buffer in VFP is needed to make it possible to change data without losing the possibility to get the old values.

CURVAL returns the values from the first layer.
OLDVAL returns the value from the second layer.
The actual value is returned from the third layer.

When not using buffering, The VFP model is exactly the same as in Fox 2.x. Because the changed data is (mostly not always) directly written to the disk, OLDVAL en CURVAL return the same values when buffering is set off.

Regards,

Walter