Russell,

>VFP6 had a much better OOP environment than VB6. However if you compare the object model of VB.NET with VFP7 it appears to be far superior. Despite claims that VFP7 is a big improvement over VFP6, I have not seen much change in it's Object model. You only have to look at VB.NET's object model of a Grid in detail (if you can figure it out) to see that it is now far superior, while MS have not spent even 5% of this effort in improving VFP's model in VFP7.
>So - finally I have started to accept that VFP is going to be overtaken by a much more powerfull OOP environment.
>I am still a VFP die hard, but feel my weapons are getting outdated. I would like some alternative views.

Are you faulting VFPs OO capabilities or the OO tools delivered with the product? Yes, I agree that other tools have better grids, or better toolbars, etc. etc., but that does not make those other tools themselves any stroger than VFP in the OO arena.

I am not saying that VFP is the end-all be-all for OO stuff. Some people insist that because it doesn't have operator overloading or multiple inheritance that it is weaker. I personally do not think mult- inheritance or operator overloading are important. VFP offers a simple syntax for creating objects, supports inheritance, and packages everything nicely.

That being said, I do wish the graphical control base classes could be more easily abstrated and that ActiveX controls were better-supported. But just because VFP has a weaker amount of available controls (due mostly to it simply being a less-popular tool), I wouldn't say that it is weaker on OO.

JoeK