The way it was explained to me is that OOP is doing things upside down. Instead of taking a function and throwing data at it, you take data (or an object) and throw a function at it. In otherwords, an object should be responsible for itself. For example,
? WVISIBLE("MyForm") as opposed to ? MyForm.Visible
>I've been told that w***() functions (wontop(), wparent(), etc) are not OOP, but I don't understand why.
>
>It seems to me that the arguments that I've heard could be applied to just about any function that existed before OOP.
>ie: "srows()" existed before OOP, so does that make it non-OOP?
>How is that different than "wparent()"?
>
>What am I missing?
>
>TIA
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer