Great post, Eric!

But I would differ with your assertion that it's bad to code classes that depend on the existance of oApp. For one, you can always test for it's existance; for two, if you follow a specific methodology you should know upfront if oApp will be used.

Much as I like to encapsulate object function into the object itself, there are times when you have marshall or aggregate multiple objects. In these cases, assumptions about the environment have to be made.

In re the original issue: I just can't abide by mixing PROC files and object methods out of personal preferenced. I have worked very hard the last few years in adopting OOP standards of development and I am not about to give them up for a questionable increase of speed in a PROC.

As to wearing out your welcome: Haha.....contrary opinions IMHO are always welcome because we all learn a little (or a lot) from everyone else. I, for one, do not take it personal if you totally disagree with me. Nor should anyone else :-)