>Are you whining again at this early stage? You have to understand that VFP is >being marketed as a tool to build data-intensive components. MS is putting a >lot of effort to enable VFP to be significantly important in VS family but as
>much as possible it does not overlap with VB and other tool's marketability >features.

I am not whining if I say that MS is putting more money in VB then in VFP this is a simple fact. I have been programming in VFP for several years now, been to devcon once and love it's community and the language itself. I realise they are still putting a lot of effort into VFP.

>What I understand is that MS solidifies the role of VFP as middle tier in an >applications built with Visual Studio.

If VFP is so strong in the middle tier then why does VB COM code run faster then VFP when in comes to transactions? Why would you ever consider using a language without multithreaded capabilities as THE middle tier platform ?