>Someone said this years ago in a previous life of this topic..."why not just take VFP call it VB, the marketing guys would like it, the VB developers would finally have a real language (and a fast data engine) and life would go on." (Les Pinter, I think)
>
>I say, let's do it and then we can charge *huge* dollars as training consultants to all the VB guys as they struggle with their first OOPS projects.

Hey! We don't need VFP renamed to do that! Actually I think there would be a fortune for all of us consulting on OOP principles to VB people.

When I was at the DevDays, ina conference about VB.Net, I could see VB people looking amazed/confused at the presentation while all of the VFPers there yawned. They went out SO excited, and we went out chatting about how many pitfalls we saw at the implementation.

I looks like it could take us just a week or so to be up and running with the basics (no pun intended) of VB.Net, even without much previous knowledge of VB, while it surely take months to most VB developers.

What an opportunity, comrades!