>
I'm certainly not marketing expert, but based on what I've seen over the recent years I get the impression Microsoft could care less if they ever had one additonal VFP customer.
<

Yep... What took you so long to figure this out... In case you did not realize it, many VFP customers have been transformed to MSDN customers...

<<
Personaly I think this is an increadably risky and foolish move. There is a whole new generation of developers who won't be using VFP...and it will die because of it.
<<

From the perspective of MS shareholders, why is this a foolish move, especially if:

1. VFP developers are not likely to go anywhere else and
2. Significnant numbers of VFP developers have become MSDN customers and
3. Many VFP developers will get on board with .NET within the next few years


<<
Even if it's the 'better tool' for the job, organizations will choose not to use it because 'no one else does' and they wont be able to find any entry level programmers who want to mess with it. Furthermore as this pattern progresses you're going to loose existing VFP customers for all the same reasons - myself included!
<<

So basically, you are asking MS too keep the product alive for the sake of keeping it alive... All of this in spite of the fact that MS has gone in a different direction that does not include x-base desktop windows apps as the focal point of the strategy..

There is no interest in growing the VFP market. You have heard it from the source. Hopefully, there will be no more confusion on this...