>Ack! Careful, you'll get the VFP OOP Standards people on you :-D
>
>Seriously, if that's what your comfortable with and it works and no one else has to support your code, then fine. But I don't think that it's fair to state that you should restrict your application object.

Alrighty Buddy, the time has finally come that I think I'm going to beg to differ with you :)

I was beating up on this same subject a few months ago, my gripe was that my oApp was either A.)monster do-it-all and the performance hit became obvious when user given ability to have multiple forms open at once, OR B.)just a container for a few global values. I was trying to decide which approach was better, and if it was B.) then why have one at all. My favorite fox person gave me a tip that the AntiPatterns book addressed this same argument, about oApp being not so good OOP practice, and I sort of put the whole issue on the shelf until I can get my hands on that book.

Despite shelfing it I made up my mind anyway :), and I really think that loading up oApp as the Keeper of all Stuff isn't good OOP because you end up with 1 object that knows all/does all, and other objects need to depend on oApp. I would much rather have better encapsulate in individual objects like your suggestion of using _Access and _Assign to down scale oApp. Plus I agree with John Henn, there is still a place for procedure files. IMHO OOP is merely a programming methodology that is not exclusive and is not a complete 100% replacement for procedural handling. Why should I instantiate an oApp heavy with methods I *might* need when I can use a standard procedure file for all my different apps and only tap (or instantiate with Feltman's Command Class tip) what I need when needed?

And as far as if somebody else has to support my code, I've lost quite a few days digging through a monster oApp just to find out what I'm looking for isn't there in it's evolved state, but rather a pointer to what I'm looking for is there and then the search starts all ove again. Days like that I was stomping my feet b***ing endlessly that we didn't have a common procedure file for generic all purpose stuff.

yeahyeah... my highly inflated $.02US worth =D)