(Holding head in hands) No one is talking about supporting VFP over VB. What has been discussed as the #1 role for VFP for over a year now has been middle-tier. You know that, I know that.

So, if an official MSDN webpage sort of comes right out and says that you are not prepared for a major new technology unless you have been using VB or VC++ in your middle-tier (and we know that's wrong), then it helps to defeat attempts by you, me, the Fox Team, or anyone else to promote VFP as a player in n-tier applications.

No one is saying rate the relative tools, just list what can do what!

>They support it. They just don't actively promote it. Two very different things. One does not imply the other. It has never been a secret that MS will not promote VFP over VB. It is neither good or bad. It is what is...
>
>
>
>
>>I'd rather say it's time for MS to support the product they sell and at least include it in general Visual Studio topics like that one. Mainly I'd agree with you in this area, but this statement of theirs conflicts with documents in the VFP MSDN area and --- which is right? Or do you like MS makijng your job as a consultant and technical advisor to your clients more difficult?
>>
>>>Do you honestly think MSDN does not have a clue? Or, more accurately, do you think this is a deliberate and conscious thing? Remember, nothing up there happens by accident.
>>>
>>>The folks at MSDN know very well what VFP's abilities are....
>>>
>>>Time to wake up and smell the coffee.....
>>>