>>>>>>>>[...] in order to set a table's buffering to any mode other than 0 (zero), SET MULTILOCKS must be ON. [...] you can't turn on any buffering with SET MULTILOCKS OFF. (As the help and docs on buffering say.)
>>>>>>>>
>>>>>>>>My US$.02 worth.
>>>>>>>
>>>>>>>Does it default to on or something? I never set multilocks to anything and I've got buffering on almost all my tables. I set it in the DE or set the form's default, so maybe it's doing it for me?
>>>>>>
>>>>>>Er, um, ahh ... that's a good question ... no, it defaults to OFF ... do you have MULTILOCKS=ON in your config.fpw? Did you, in Tools/Options/Data tab, check the box which says Multiple record locks, and click the "Set As Default" button?
>>>>>>
>>>>>>Cheers,
>>>>>
>>>>>I don't have a config, and the options one is not checked.
>>>>>
>>>>>-Michelle
>>>>
>>>>Help: "MULTILOCKS must be ON to before row or table buffering can be enabled with CURSORSETPROP( )".
>>>>Does it mean that in other situations (i.e. you don't use CURSORSETPROP) you should not bother?
>>>
>>>That seems to be the case. I don't use CURSORSETPROP. All my buffering is through the DE or through the form default. I just double checked my "SET" code and it's not in there.
>>>
>>>-Michelle
>>
>>If you do DISPLAY STATUS in the Command Window, do you see MultiLocks = on ?
>
>Nope. They're off.
>
>-Michelle

Maybe it is your private data sessions, then. It makes no difference to me, I've always had multi-locks on for other reasons...