The point I was trying to make is that if you are using ADO to talk to SQL-Server, you should not be doing it through ODBC. Instead, use the OLE-DB Providers. It is much faster and much more reliable.


>Hi Josh ---
>
>Whew....JVP's post caused me to question my sanity :-) Thanks for the info!
>
>>
>>From the MS web site: "The MDAC typical redistribution installation contains the core components (ADO, OLE DB, and ODBC) and additional OLE DB providers and ODBC drivers for various data stores." I've never been able to find any list of all of the drivers and providers included, but I know that it has the latest VFP and SQL Server ODBC drivers.
>>
>>
>>>Hey John,
>>>
>>>When I ran MDAC_TYP.EXE in conjunction with SP3, *something* updated my OIDBC drivers. The answer was a shot in the dark :-)
>>>
>>>>
>>>>MDAC refers to the Microsoft Data Access Components, which is concerned with OLE-DB, not ODBC.
>>>>
>>>>
>>>>>Nabil ---
>>>>>
>>>>>Try downloading MDAC 2.1 from Microsoft. It's the latest drivers and may help.
>>>>>
>>>>>
>>>>>
>>>>>>We have upgraded SQL 6.5 to 7.0 on above server which is replica of our existing live server (SQL 6.5).
>>>>>>Now when we are trying to run the existing applications (which are running fine on 6.5) on the new 7.0 server we are facing following problems...
>>>>>>
>>>>>>1. Using ODBC 2.65.0201/0240, our acces to SQL 7.0 is very slow
>>>>>> ( we installed ODBC 3.7x.xxx to connect to SQL 7.0, our finding are still very slow and we could not connect to SQL 6.5)
>>>>>>2. Our view's and form's loading are extremly slow
>>>>>>3. We are facing problems with one particular form which is having a view with following SQL statement...
>>>>>>
>>>>>>*********
>>>>>>SELECT Mm_srvhead.iYear, Mm_srvhead.iSrvNo, Mm_srvhead.cStore,;
>>>>>>Mm_srvhead.dDateRecvd, Mm_srvhead.dDocDate, Mm_srvhead.iPoYear,;
>>>>>>Mm_srvhead.iPoSerial, Mm_srvhead.cPoInd,;
>>>>>>SUM(Mm_srvitem.rDhValue) AS rdhvalue, Mm_srvhead.lDocCommit;
>>>>>>FROM dbo.MM_SrvHead Mm_srvhead, dbo.MM_SrvItem Mm_srvitem;
>>>>>>WHERE Mm_srvhead.iYear = Mm_srvitem.iYear;
>>>>>>AND Mm_srvhead.iSrvNo = Mm_srvitem.iSrvNo;
>>>>>>AND (Mm_srvhead.iPoYear = ?v_POyear;
>>>>>>AND Mm_srvhead.iPoSerial = ?v_POSerial;
>>>>>>AND Mm_srvhead.iYear BETWEEN ?v_frYear AND ?v_toYear);
>>>>>>GROUP BY Mm_srvhead.iYear, Mm_srvhead.iSrvNo;
>>>>>>ORDER BY Mm_srvhead.iYear, Mm_srvhead.iSrvNo
>>>>>>*********
>>>>>>we run this view on the SQL 7.0 query analyzer, it gave us error related to TRACE flag 204, and the query was aborted.
>>>>>>
>>>>>>4. Speed of data acces to the server is our main concern
>>>>>>
>>>>>>Please advice us how to overcome these problems, and which ODBC driver is best suited for our environment.