>I was wondering if someone knows what (conceptually under the hood) happens when you set buffering to a cursor (not a table but a local cursor). Does VFP create another cursor exactly the same as the original one? The reason I am thinking that VFP possible duplicates the cursor (when setting buffering) is to be able to get the Old Value if a column value is changed.
>
>Thank you in advance for any input.

Dmitry,

Fox always had buffering in memory for editing data in a table. Prior to buffering being available to us to manage it wsa handled by Fox internally. When you create a cursor VFP creates a presense on disk if it needs it, but it also keeps a memory image of the data. VFP knows what the values of the fields are now and what they were before they were edited regardless as to whether you have buffering enabled or not. When you set buffering on you are enabling your control over these memory buffers you are not creating them as if they weren't there before.