>>>The right tool for the right job. Right? Sometimes PUBLIC is most desirable, and my response to Koen was
>>>to his comment "don't use public," which I do not believe is good advice as it immediately shuts people off
>>>to the idea of ever using a PUBLIC definition, when using PUBLIC definitely has its place.
>>
>>That does not mean use every tool. Name one time where public is the most desirable.
>
>goApp.

I wonder if that is necessary to declare goApp as PUBLIC. Private would work as well, when goApp is instantiated in the main.prg before READ EVENTS, at least that's what I'm doing now.