Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL ACCESS --2000 vs. 2003

Status
Not open for further replies.

MChrisM

MIS
Dec 8, 2004
17
US
HHello --

I have a pretty basic ASP app where I pull some data from SQL 2000 I have one SQL server running on Windows 2000 and another on a Windows 2003 Cluster --
When I use my connection.inc file to connect to the SQL server running on 2000 everything is happy -- but if I change the connection string to point to the SQL 2000 instance running on the 2003 instance the script times out.

***CONNECTION STRING (CONNECTION.INC)****

connobj.Connectionstring = "DRIVER=SQL Server;SERVER=AAAA;Database=TTTT;UID=xxxx;PASSWORD=xxxxxx;"

Now if I use a inc.asp file that I wrote below ---

***(INC.ASP)***

CreateObject("ADODB.Connection")
Connobj.Open "Provider=SQLOLEDB.1;" & _
"Network=DBMSSOCN;" & _
"Data Source=AAAA;" & _
"Initial Catalog=TTTT;" & _
"User ID=xxxx;" & _
"Password=xxxxxxx"
I can connect just fine though I eventually get an error when I begin to manipulate the data

So my question is

1) what is the difference in the two access methods

2) why will this work when accessing the 2000 server and not on the 2003 server -- the SQL instances are Identical on both servers --



 
1st one is using the ODBC driver: [tt]DRIVER=SQL Server[/tt]

2nd one is using OLEDB driver: [tt]Provider=SQLOLEDB.1[/tt]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top