>>John,
>>
>>I completely agree with you. Marketing never existed. The best marketing for VFP has been that it's part of VS. It allowed me to use VFP on projects because the customer owned the product.
>>
>>The only valid reason IMHO is that VFP7 could be released earlier. But then it might be the last...
>
>But... if it launches with the rest, the team has plenty of time to receive beta feedback and maybe add a couple more goodies. Can you imagine how good it would be to have some extra months just for debugging?!

The fact that MS even put the question as to whether we want VFP included in the .net platform raises a hundred flags. Obviousely, they are having second thoughts about the products future viability in the IT community. Whether you take it out or keep it in makes no difference. Perception will ultimately decide its fate. Foxpro will live, but always as a tertiary language without much respect.