This is absolutely not true. While accessing data via ODBC over a WAN is
slow and cumbersome (made worse by slow connections), if data packets are
lost its not a factor of ODBC. Of course, using efficient queries via ODBC
improves the transfer time.
We use ODBC connections across our WAN every day, all day.
Re: ODBC TIme Out MSACCESS<-SQL2K ...Gruss... > ich habe ein Time Out Problem bei einer ODBC Verbindung.... die WAN Leitung ist einwandfrei und hat gute Antwortzeiten. ...Next by Date: ... (microsoft.public.de.sqlserver)
ODBC TIme Out MSACCESS<-SQL2K ... Ich habe bereits bei der ODBC Connection die TimeOut Schwelle auf 180 sek ... die WAN Leitung ist einwandfrei und hat gute Antwortzeiten. ... Prev by Date:...Next by Date: ... (microsoft.public.de.sqlserver)
Using Excel OS 9 to connect to a WAN data source ... Microsoft's Merant ODBC 3.5.1 software patch as the ODBC connectivity ...Excel/Query connects in seconds after I enter ... However if I go into my ODBC DSN and change the Server Name and Server ... Address to the WAN ip of my Win2000/SQL 2000 server, ... (microsoft.public.mac.office.excel)
Using Excel OS 9 to connect to a WAN data source ... Microsoft's Merant ODBC 3.5.1 software patch as the ODBC connectivity ...Excel/Query connects in seconds after I enter ... However if I go into my ODBC DSN and change the Server Name and Server ... Address to the WAN ip of my Win2000/SQL 2000 server, ... (microsoft.public.excel.misc)
Using Excel OS 9 to connect to a WAN data source ... Microsoft's Merant ODBC 3.5.1 software patch as the ODBC connectivity ...Excel/Query connects in seconds after I enter ... However if I go into my ODBC DSN and change the Server Name and Server ... Address to the WAN ip of my Win2000/SQL 2000 server, ... (microsoft.public.sqlserver.clients)
