> Easy fix, but could still be a PITA if I need to trigger an action or setting based on only the existence of a variable with no need to actually get/set the value. I say this figuring that with a globals collection I'm not going to just dump every single thing into it on startup like I would with custom properties, instead I would stuff it as needed. So what I would do is in addition to my Get/Set methods I would do a CheckGlobal() or something similiar to handle the prelim 'does it exists?' question. I guess the extra method still adds complexity but I think I would rather have to remember an extra method name as opposed dealing with the visibility issue in both Get() and Set(). What do you think?

I like it, I should also point out that it'd be wise to have a Remove() method as well, incase you store an object reference in it that needs to be removed.

Of course, all of this leads me to conclude that we should be talking about oApp.oGlobals rather than a property array, so that the application object's UI doesn't get clouded with all of the methods related to the globals collection.