>VFP supports Inheritance,Encapsulation,and Polymorphism that makes
>it a perfectly good OOP tool

I'm sure a lot of us appreciate the certain OOP qualities VFP possesses, but I wouldn't go so far as to give it full credit for OOP support.

For instance, with regard to encapsulation, I think VFP could have benefitted from some kind of 'private/public' property mechanism. It DOES get confusing when you sometimes set an object's properties at design-time or programmatically, only to find out this was supposed to be an 'internal' aka 'private' property that get's totally overwritten by the object's internal code. Similarly, how do we protect our internal properties from user modification? How come there are public/private variables with respect to functions and procedures, but not to objects?

[continued...]