Thank you!

I changed it to...

use config in 0 shared
select config
CURSORSETPROP("Buffering", 3)

...and it works fine. Isn't the table that I'm "use"ing being selected by default?

>>I'd like to ditch the DE and set up my environment in code. It's a simple task and I've also used udDE for verification that I did it right. Where
>>can I put the code though? I have an application object that has a method "CreateDE" that I put the code. Here's a look at the DE code...
>>
>>use config in 0 shared
>>=CURSORSETPROP("Buffering", 3)
>>
>
>Aside from what Larry told you, just from these two lines - are you sure that config is exactly the table which is getting buffering set? You'd better
>
>select 0
>use config shared
>=CURSORSETPROP("Buffering", 3)
>
>...just in case, so that you'd know that it's really your table that the CursorSetProp is operating with.
>
>A better location to call such code from would be, IMO, each individual form's .Load method, so you could have different settings for each of your forms - so you could open your tables read only or under a different alias etc, as needed. If you do that at the oApp level, it's all the same throughout your app, and any order change, filter or whatever you introduce in one form, will affect any other form open at the same time. They didn't invent private data sessions without a reason.