>It is now possible to write VFP on the CLR: the IronPython project is working on the 4th beta. In fact, Microsoft is hiring people to port dynamic languages to the CLR, building on the work with IronPython: http://members.microsoft.com/careers/search/details.aspx?JobID=6D4754DE-11F0-45DF-8B78-DC1B43134038
>
>With that in mind, I wrote Milind Lele (Milind.Lele "at" microsoft.com), the new VFP Product Manager, as I had written Ken Levy when he was in that position, lobbying for VFP's inclusion in the list of languages to be ported. As I expressed it to Milind, while VFP's features are in the process of being ported to Visual Studio, there is a business benefit to MS to have VFP continue to lead the way in RAD data-oriented development. Not to mention the benefit to those of us whose business model is based on having that kind of development environment available.
>
>Milind's response was straight-forward: "Current plans for the future of VFP are what we have announced in the VFP roadmap and we will periodically update the plans. How these plans change will be driven by feedback similar to what you have written."
>
>So if you want VFP to have the best of both worlds, now would be a good time to let Milind know. It's no longer technologically infeasible: it's only a matter of resources.
>

Hank,

You are tilting at windmills. I agree entirely with what Craig and Alex said. Microsoft could not possibly have made it more clear that FoxPro is no longer a strategic product. It will tick on for a while in legacy mode, with good money still to be made by those with the right skill set and/or the right clientele, but Microsoft has more or less closed up shop. They have said there will be no more new versions. They have virtually disbanded the team. Exactly how many tea leaves need to be read?

One of these days we will be told Calvin has moved on and then we will all really, really, REALLY get it. FoxPro may not exactly be dead yet but it has been taken off the respirator.