>No way -- the end of development came due to lack of revenue stream. MS is a business and like all businesses, they only pursue avenues that will make money. The VFP community was its own worst enemy in this -- how many developers are still on VFP6? How many bought upgrades for VFP7, VFP8, and VFP9? From what I have read -- most VFP applications are still on VFP6. I have developed tools for VFP9 and many developers have asked for backward compatibility with VFP6 -- why because they don't have VFP9 (let alone 7 or 8).
>

I would agree with that, but its just the half of the truth.
MS could not make money just with the existing "VFP community". It was necessary, to get new VFP customers, but the product itself was everything else than interesting for other developers. (IMHO the report designer extensions was a complete waste of time and money, because absolutely not interesting for non VFP developers)

Also MS gave bad signs to the community, starting with VFP 7.0 and its removal from Visual Studio. Not talking about the discontinuation of localized IDE and help file as well as realizing dubious wishes from the VFP community wishlist or extending the "SET" command and "SYS(...)" function common grave.