JimN:

>Just how do you know that "it would require a complete re-write of VB"??? And even if it did, did we not get a complete re-write of FP with VFP 3??? Also, though I hardly paid attention, it seems to me that VB got some heavy re-writing between versions 4 and 5 and 6. Seems to me that the VB 'team' is (probably) staffed to rewrite VB at every release.

It would. Logic dictates that as well as VB gurus from Microsoft have said that in articles in VBPJ and other magazines.

>Your "MS has seen Fox programmers struggle with OOP..." may be true (who can say?) BUT it contradicts a statement you made a few days ago that the LAST thing someone coming from FP should learn is OOP. I wonder why the same wouldn't apply to VB and real OOP??? I wonder why the VB team could not engineer a new VB with full OOP in such a way that all of the old stuff would still work??? Is it only the VFP team that can do that???

MS had nothing to lose and everything to gain moving FP to VFP....the reverse is true with VB ... the general VB community seems to want inheritance and all the other constructs that we have that they don't but they find ways to work around them. Can you imagine the nightmare if MS made wholesale changes to the way VB operates and it breaks all the myriad of applications running in VB, using VBA, or VB Script? To gain what?

Your argument makes little sense, Jim.