RE: ADO and Proxy Server
ingo_at_nospam.com
Date: 02/26/04
- Next message: Mark Bennis: "DBF"
- Previous message: Pardeep Kadian: "ADO"
- In reply to: Kevin Yu [MSFT]: "RE: ADO and Proxy Server"
- Next in thread: Kevin Yu [MSFT]: "RE: ADO and Proxy Server"
- Reply: Kevin Yu [MSFT]: "RE: ADO and Proxy Server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 06:31:10 -0800
Hi Kevin,
Thanks for your reply. No, I definitely can't use port 1433 as it is being blocked, but I know in my connection string I can specify any port I want. As an example, in our office we don't have a proxy server (this is for a client application), but just a firewall doing NAT. I configured our SQL server to listen on port 80. From outside the firewall, I used the following SQL connection string:
oConn.Open "Driver={SQL Server};" & _
"Server=xxx.xxx.xxx.xxx;" & _
"Address=xxx.xxx.xxx.xxx,80;" & _
"Network=DBMSSOCN;" & _
"Database=myDatabaseName;" & _
"Uid=myUsername;" & _
"Pwd=myPassword"
Which worked great. But it fails when I put it behind a proxy server and try and configure socks to go through port 80 as well.
Again, is there a different way to approch the problem perhaps? My end gola is to do a bulk upload from Access to SQL server. I know I could do some form of web service, packaging the data on one side, and unpackaging/importing it on the other, but my preference would be to make it as simple as possible.
Thanks,
Ingo
- Next message: Mark Bennis: "DBF"
- Previous message: Pardeep Kadian: "ADO"
- In reply to: Kevin Yu [MSFT]: "RE: ADO and Proxy Server"
- Next in thread: Kevin Yu [MSFT]: "RE: ADO and Proxy Server"
- Reply: Kevin Yu [MSFT]: "RE: ADO and Proxy Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|