It's an old arguement, similar to the "you should never use PUBLIC variables" discussions that have been going on since VFP 3.0 was released. My advice is to do what is best for your situation.

>Hi Craig,
>That actually makes sense to me. But it leaves a few questions.
>
>To borrow a quote from Marcia Akins.
>Does OOP demand that we "crack walnuts with a sledge hammer" rather than use one of those functions that you have to throw data at?
>
>Example:
>It appears that there is no 'simple' way to replace wParent() and wExist() in OOP. It's possible to design an 'window tracking system' to get at that information, but it's overkill unless you need that system for other things.
>IOW: Designing a 'window tracking system' for the SOLE purpose of replacing wParent() seems to violate a more basic principle; "KISS".
>