>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,

Read my other reply to you for details.

*Startup program

PUBLIC oApp
oApp = CReateObject("MyApp")
READ EVENTS

is functionally no different than;

*Startup program

PRIVATE oApp
oApp = CReateObject("MyApp")
READ EVENTS

except that the former can interfere with things that are outside of the application because it doesn't go away automatically when the app ends.