That's a good idea to tie to _Screen, George. I use a Global App Obj and attach properties for systemwide usage to it; I have also run into the need to CLEAR ALL, which can make the Global Object go Bye-bye....

>>Hi Sergey!
>>
>>>The good practice is not to use public variables at all.
>>
>>Why?
>
>Fernando,
>
>The reasoning has always been that it can be very difficult to determine where a global has been changed.
>
>Personally, I don't use them at all. Anything I need globally, such as an application object, I make a property of the _SCREEN. There is one very nice plus to this, BTW. I've run into some instances where automation server references aren't properly released. The solution here is to issue CLEAR ALL. Unfortunately, you can't do this with global variable because their values will be cleared. However, system variable, such as _SCREEN, aren't affected by this.