>In response to the OP, why would VFP going away matter? We are Programmers, and we write biz apps and data-centric apps. VFP is our tool (granted the tool of choice for many of us). This is no different than the VB hysteria. If you can write code, you can do it in any language. You might have some learning to do, but oh well. You had to learn VFP too.

Even if VFP is kept intact, it is likely to undergo many changes, as it already has just from 2.6. Heck, we supposedly do 90% of our work BEFORE writing a line of code. Turning p-code into source code is a minor issue, and there are tools that can do that for us.
In a typical month, I might work in 4 languages. It's not untill after the design that the choice of language matters. The split might even be better for VFP and make it less OS dependand, increasing our 'customer' base to any OS.

That all said, I have some concerns about how stuff would be implemented, esp. from the OS side of the new M$. Would they start licencing API functions? Make programmers pay for the privilage of writing code for their OS? Maintain seperation of applications from the BIOS?