> Wow Mike. Heh... I was on my way home for the night and now you just got my wheels spinning into overdrive. My first thought is I *think* like this approach, but I would have to consider visibility and debugging a little to make up my mind for sure. For example, if I'm using an oApp property who's value is giving me some grief, I can usually find the offending setter of that value and solve my problem fairly quickly. But now using a Globals Array with Set/Get methods presents me with an extra layer to dig into. No way I'm going find my problem with pausing live code. Not that that's a big deal, just a thought. I think I need to think on this awhile, but I do like it!

I implemented it in a custom app I was working on because the previous developer had over 100 items that he wanted to add as properties to the application object. I figured there had to be a better way to manage it, and this is what I came up with. I can't decide if it's something that we want to put into our base application class for VFE or not. For me it's kind of a nagging issue because it does add a layer of complexity, but it would eliminate the possibility of a developer adding a custom property that we subsequently add in an update.

Having supported people working with our application object for a long time, I've seen how custom properties tend to proliferate on the application object.