Michael,

I find that I don't really need that many SETs, since most of my code runs in private DS and my lower level form classes SET things up it's a non-issue. I also find it much easier to have my dev SET environment the same as the app environment.

It's also worth writing SET independent code whereever possible. like using == instead of consantly messing around with turning EXACT ON/OFF.

>I have a class to hold all the settings when my app starts up and sets them up the way I want for development or runtime. To this I've added a a couple of functions to push/pop settings into a collection. Since this object is part of my app object it is more versatile that a local save.
>
>That said... if you dont have this in place just code it to a local variable as David suggests. It only takes a couple of lines of code.