Colin,

I always thought the BufferModeOverride was used to determine at initialization what initial
BufferMode was used (the form's or the cursor's). Anytime I wanted to change the
buffering I have used CURSORSETPROP([BUFFERING], 3, ALIAS()). I have never
verified whether it changes any property in the DE. Likewise, I do not think that if you
leave BufferModeOverride to 1 (form buffer mode) that it will automatically sync the
BufferModeOverride property to the form's specified buffering.
-myron kirby-
=========================================
>Thanks Myron, this appears to be working. At least the message stops coming up. However, this raises another question for me that I hope you can answer. If the form is using Private DataSession, which takes precedence, the buffering value assigned using CURSORSETPROP or the DE.BufferModeOverride value?
>
>>Colin,
>>
>>This is what I am doing:
>>
>>

>>
>>lcSafety = SET([SAFETY])
>>SET SAFETY OFF
>>
>>SELECT v_Cust
>>lnBuffer = CURSORGETPROP([BUFFERING], ALIAS()) && Save buffer mode
>>=CURSORSETPROP([BUFFERING], 3, ALIAS())        && Optimistic row buff
>>
>>*--Index
>>INDEX ON DELETED()                      TAG Deleted
>>INDEX ON RecKey                              TAG RecKey
>>
>>*--Clean-Up
>>SET SAFETY &lcSafety
>>=CURSORSETPROP([BUFFERING], lnBuffer,ALIAS())   && Turn buffering off
>>
>>

>>-myron kirby
>>================================================