>You can also put this information in your form class (Load or Init methods) if you use one. However you must be sure you don't overwrite the code by adding new code to the method without calling the baseclass code.

Yes, I decided to do both :-)

I wrote a EnvMgr class for all the settigns not scoped to a datasession.
And a ScopedEnvMgr class for all the settings scoped to a datasession.

The application creates an instance of both, pointed to by variables goEnv and goScopedEnv.

Each form is based on my form baseclass, xFrmStd, which has a user defined property oEnvMgr and has oEnvMgr = CREATEOBJECT("mcusScopedEnvMgr") inthe LODA() of the baseclass form.


So maintenance of the environment manager is in the class designer.
And the maintenance of the use of it is in the form designer.

I'm getting used to that split - it's a big change from FPDOS 2.6 <g>