Thank-you!.

I contacted MS on this issue. Waiting for a callback... I will let you know of any resolution.


>I see. I saw yesterday on the sql.ru forum the same sequence of calls to sp_datatype_info on the insert command. I think it's more a question to MS about this implementation.
>
>>Actually, there is no SQl statement in this test.
>>
>>In VFP 8, i did this in the command window:
>>
>>

>>lnHandle = SqlConnect("MyDsn")
>>=SqlDisconnect(lnHandle)
>>

>>In Profiler, i can see:
>>

>>Audit login
>>select USER_NAME() select usertype,type,name from systypes where
>>Audit logout
>>

>>
>>I do the same in VFP9
>>And the result in profiler is:
>>

>>Audit login
>>select USER_NAME() select usertype,type,name from systypes where
>>exec sp_datatype_info 1
>>exec sp_datatype_info 12
>>exec sp_datatype_info -2
>>exec sp_datatype_info -3
>>Audit logout
>>

>>
>>
>>>What is your select statement? Can you try to specify field output types
>>using CAST ?
>>>
>>>>Hello,
>>>>
>>>>In VFP 9 SP1, everytime we issue an SqlConnect() or an SQLStringConnect() i see in SQL profiler (for both SQL server 2000 and 2005) the following:
>>>>
>>>>

>>>>select USER_NAME() select usertype,type,name from systypes where usertype>=257
>>>>select USER_NAME() select usertype,type,name from systypes where usertype>=257
>>>>exec sp_datatype_info 1
>>>>go
>>>>exec sp_datatype_info 12
>>>>go
>>>>exec sp_datatype_info -2
>>>>go
>>>>exec sp_datatype_info -3
>>>>go
>>>>

>>>>
>>>>In VFP8 only the first 2 line are present. It is hurting performance on our application (VFP9 SP1 dll's under COM+ application)
>>>>
>>>>Anyone know how to avoid the 4 calls to "sp_datatype_info"
>>>>
>>>>Thanks.