John,

>First off, if Fox 2.x could be made OO in VFP, so could VB... It is not a technological issue. When MS is ready to do it, it will be done....

Fox 2.x is not VFP. IMO (and if you ask anyone else who made the jump) they're two total different animals. Sure, to some extend VFP is upwards compatible with FP 2.x

>From a business perspective, MS is too committed to the VB franchise. VB is here, and it is here to stay. If there are improvements, there will be a migration path. No way MS will rock the boat here...

If VB goes fully OOP (in the way VFP did) this means a great step forward. I will probably require a total rewrite of the product. To me it's NOT VB anymore, even if it's upwards compatible with VB x. I'm not sure what would happen to the derived (script) languages like VBA.

And if this new version of VB adds a local database engine in the VFP manner, I'll bet you see a product that looks very much like VFP and indeed give developers reasons to make the step to VB. Until that time I'll sit and wait....

>It is not me who has his head in the sand....<s>......

Who is? I sure don't feel any sand on my head.. < G >


Walter,