George,
After checking, same here with cursor.buffermodeoveride=5, but,
cursorgetprop("buffering")=1
Nothing I could think of would change that, except I finally used:
set multilocks on
select mytable
cursorsetprop("buffering",5)
and that worked.

>>existing form that had the dataenvironment stripped out. When I used the DE I had generated with the form, I started getting errors telling me that buffering was required.
>
>So I looked at the code to check to make sure that it had been generated properly. The InitialSelectedAlias was right (and in fact was current when the error occurred), and, sure enough, the BufferModeOverride was set to 5 for the cursor object.
>
>Figuring something in the form might be doing it, I generated the session object without the form, and checked CURSORGETPROP() to see if it was right. It wasn't, it was set to 1. Back I went to staring at the code.
>
>I noted, both from the code and the metadata, that CursorSource property appeared (and was initialized) after the BufferModeOverride property. On a hunch, in the code I physically moved the CursorSource ahead of the BufferModeOverride property, and tried again. This time everything worked just fine and the property was set correctly.
>
>I don't know if this effects anything prior to VFP 6.0 SP3, but apparently, in this version, the order that some of the properties in a cursor object are initialized is significant.