I dunno.... MS could call it whatever they want to....but, like anything they create, if they DON'T back it up with the $$$$$$$ in advertising and promotion, it won't get any more users (developers or end-users).

I wish they would give Ken the big bucks for advertising and promotion. But most of that is going to .NET itself.

But VFP is doing quite well (in fact, great) considering the money it gets... they are working on a new version, are in the planning stages of 9.0, getting better coverage on the web, still have great conferences, and have our own EXCLUSIVE line of great books from people who actually USE the software for a living (Will's books).

I wish it was better. I honestly do. But I don't think changing the name will help. Even it could, MS would have to cough up the money to promote it.

Tommy

>I think MS won't name it VFP for .Net till they can back up this claim. As MS is the iventor of this term, that would make their job a little easier.
>
>I think from a marketing view point, choosing this name can be a win win situation for VFP and hopefully that will bring MS to market VFP more agressively. Before .Net, there was no advantage of VB over VFP as far as capabilities, I'd even go further to say that VFP excelled over VB in many respects but the marketing muscle of MS made VB what it is today as a lot of 3 party products such as Crystal Reports and a lot of slick ActiveX were introduced to the market fully tested for VB but bug ridden when used in VFP adding further to the imbalance.
>
>A pet peeve for VFP community was MS doesn't back it up as strongly as it should, adding '.net' would entitle more backing by MS to VFP.
>
>How does that sound?