>>I can also see how one can do away with a lot of public variables by making them properties of the main public object.
>
>Ah, another sheep has joined the flock. That realization is one of the toughest sells I have when teaching students about application frameworks in VFP. Most 2.x developers have a hard time letting go of the old notion of having many PUBLIC variables throughout the application. Welcome to the party!

Thank you for the welcome! This aspect of OOP has eluded me for MONTHS and it was always a mystery to me. Suddenly, it's like someone removed the blindfold. Now, it seems so simple and sensible. It's also a lot easier to maintain. For example, if I have code called "oToolbar.Reset()", which I do, I don't need to hunt around my source code for where "FUNCTION RESET" is residing. Now, I can go straight to the class library! I like it!

Michael Reynolds