George, that's clever and I'll certainly use it whenever appropriate (appropriate according to me). However, I see one problem. Jim Booth stated (in other words) that we must guarantee that all variables get out of scope when the application ends, in order to prevent interference in a next run application. Added _screen properties won't get out of scope, so Jim would disagree with this usage?!

Peter

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