>While VFP's OOP design is highly functional, VFP7 has had very minor change since the release of VFP5 about 4 years ago.

What else can you improve when it is stable enough? VB.Net is a total overhaul from VB6. I mean, it was not developed on top of VB6 structure, unlike VFP7.

>It is now being overtaken by the pouring in of much richer OOP functionality of VB.NET and this to me seems to be the "Begining of the end".

How do you make it richer: VB.NET over VFP? Please give specifics. If I'll be given a choice between VB.Net and C#.Net, I'll go for the latter. VB.Net is just to keep VB'ers in the fold of MS IMO.

>Also, if you consider the improvement of VB.NET over VB6, it is over 10 times greater than the improvement of VFP7 over VFP6.

Not just 10 times and in fact, I don't see it as only an IMPROVEMENT, but a total redo. That's why you can't run VB6 and below applications "as is" in VB.NET. In short, not backward compatible.