>>>>If VFP is so strong in the middle tier then why does VB COM code run faster then VFP when in comes to transactions?
>>>
>>>Where did you hear this, or where can I find out more information?
>>>
>>
>>In the documents section there is a comparison between VFP and VB they clearly state that VB COM has less CPU time.
>
>VFP does take more resources to operate a COM server than VB, but that doesn't translate into less performance except on a resource choled machine.
>
>Also, not that I am contesting the fact at hand, but you should keep in mind that the tidbits posted in the documents section are placed there by users like you and me, who may or may not be correct, or qualified to make the statements they are making.

You are absolutely correct. I have read an article one that compared VB 6 to VC++ 6 and VJ++ 6.
VB Kicked the hell out of VJ++ but it couldn't compete with VC++ these test were not COM based. I know VJ++ COM components are a lot slower then VFP COM components trough testing.
We have an MSDN subscription and the magazine delivered with that doesn't really mention VFP. A lot of speed test you see don't mention VFP. Doing them yourself is really hard cause you need to test on one server. It could be that VFP performs better then VB when the server has more memory or the other way around. Data could be faster in VFP then in VB or the other way around. Maybe VFP is faster at handling data but you could maybe increase performance on your VB objects by using more server-side stored procedures.
There is also a feature you can activate called connection (SQL Server connection) pooling. Do you know of a way to check if VFP supports this. Somehow I have a feeling only the Connection object (COM) supports this and not the standard VFP SQLCONNECT/SQLSTRINGCONNECT connection.