>So... what I would like to hear at the keynote on Sept 29, and in Milwaukee in November, is that VFP continues to allow me to do what I need: Namely, to produce applications that don't require me to spend money I don't have, that can run against SQL Server if my customers are large enough or MSDE if they are not, and that allows me to do the lastest thing, in other words to stay in the game.
>

But you can do that today and tomorrow after VFP 8 is released. I don't think you need Ken to state this again at a keynote. I think what you want and what others want is for MS to promote VFP to the point where people would give thought to choosing VFP over VS .NET. Your goal is to not invest another dime in learning new because at this point, you have made the decision that you will not get the return on investment you seek.

Technically, everything you seek VFP does. Because you and likely others don't wish to make further investments in learning, does that mean MS should go against its chosen strategy in .NET? I don't think MS should and FWIW, going backwards is not in the sharholders best interest. What I mean by backwards is back tracking from the .NET initiative.


>
I'd also like to hear that that MS has made it easier to train people to use VFP.
<

I still train VFP developers today and I find it to be quite easy. What do you mean here???

<<
That means I like the discoverability I heard you talking about and other introductory tools.
<<

My guess is that you mean to make it easier for people to learn how to use VFP for themselves...

<<
Also, I would like not to be left out of anything potentially important, such as net services (I am aware that VFP7 allows that easily).
<<

But VFP has not been left out of web services????

<<
Last but not least I'd like to hear that inside MS there are still people that love this language, which is a work of art in my opinion.
<<

But there are people who love Fox inside MS???

What precisely are you looking for????