Doug,

I agree with you that OOP is the way - believe me - I utilize it fully. And - I agree that more than a VERY few publics (or even one) is messy. Still something has to hold my app object open - and my argument is that it might as well be a public as opposed to a private if for no other reason than with a public , I can reference it in the command window when suspended.

I still have yet to hear a reason not to do this other than essentially ... "just because".

thanks,
Ken


>Ken,
>
>Happy New Year!
>
>I'd bet that most folks would have no problem with your approach. Even then you could create your app object and pass it into your system and reference it locally to eacj object. That's what I do and the reason is that it more closely follows the notion of each object being able to sustain itself.
>
>Seems to me that whe whole idea is to use this object oriented stuff to make our apps easier to maintain and PUBLIC variables are, well, messy compared to this new capability. Mind you I've used them since late 1986, early 1987 so making the transition to using an object was something I had to think through first. Now I wouldn't develop any other way.
>
>Just one take.
>
>Best,
>
>DD