Hi Dragan,

SNIP
>I don't have that problem, either, as long as the "have to" comes from where my bread is buttered.

Which is exactly what MSFT is doing. I don't like it, but I'll get by and MSFT has the right to do as they see fit for their business. This is the opportunity for many to expand their knowledge and toolset even if it was forced upon them. (I may finally move faster on the dotnet route than I have in the past now - I am switching to vb.net instead of c# purely as a business requirement. I'll still work in c# where I can). It gives many VFP developers the support (for the 1st time in some shops) from their employers to learn a new tool and the time and support to make the move. For many, the decision to stay with VFP or to use ONLY VFP was a business decision and now it will be a business decision to plan for the future and make a change (when necessary). For independent developers, the situation is different in many cases.

Having written that, I still fully support anyone who wants to invest time and energy in voicing their request for future support of VFP from MSFT. MSFT's doing what is best for it, and our fellow developers are doing what they think is best for their business. It may be futile (no maybe about it in reality) but I still support them. I think that as long as it is done in a professional manner then it should be supported. Everyone seems to be supporting MSFT because we know it was a business decision but few seem to be supporting their fellow developers who are acting based on business needs as well.