Hi,

I tend to agree with your view on the ongoing discussion. What I think is best for both camps is to have an option for VFP the ability to compile to CLR (with some lost of functionality and other added benefit of CLR environment). With this then VFP would have the best of both worlds without being alienated by the rest of the MS development tool. Taking out VFP of VSNet IMHO would be a clear indication from MS that the product is put out into the pasture.

We have to remember that MS marketing has great influence on the enterprise and decision makers in terms of tools to use and direction to head. If VFP is to remain lagging then MS is really not going to promote it as it does not make sense. A lot of times when we do development work for our client, they would direct or choose the tools to use as they would want to use a tool that is deem current and it is easier to employ programmers to maintain it afterwards.

Regards,
Kueh.

SNIP