Hi!



You might want to try this:

Delete your DSN, reboot and recreate it again.



Also make sure you have the latest drivers.



Hth,



Hakan



-----Ursprungligt meddelande-----

Från: Marcus Hamilton [mailto:marcus@p...]

Skickat: den 12 september 2001 20:11

Till: ASP Databases

Ämne: [asp_databases] Postscript to 'Server breaking Access DSNs'





Dear All,



This is a postscript to an earlier message that said:



I'm converting over to SQL Server 2000 from Access 97, but after having

installed SQL, none of my Access ODBC DSNs work.



The operating system I'm using is Windows Server 2000 Advanced.



I get the following error:



"Microsoft OLEDB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC

Driver Manager] Data source name not found and no default driver specified."



I assuming that it is possible to run applications that use Access and

applications that use SQL Server on the same server.



The way that I'm trying to access the data in the script is:



set ors = Server.CreateObject("ADODB.Recordset")

ors.open "tableName","dsnName",adOpenKeyset,adLockOptimistic,adCmdTable





I have since discovered that whilst:



set ors = Server.CreateObject("ADODB.Recordset")

ors.open "tableName","dsnName",adOpenKeyset,adLockOptimistic,adCmdTable



does not work since installing SQL Server 2000



the following does:



set oConn = Server.CreateObject("ADODB.Connection")

oConn.open "dsnName"

set ors = oConn.Execute("SELECT fieldName FROM tableName")



The Recordset connection did work before SQL server was installed. I can't

change all of my connections to use the Connection object because of legacy

code.



Help would be much appreciated.



Regards



Marcus

He should have the latest drivers if he installed sql 200, right?



Maybe that is the case. I remember reading something about the latest

mdac didn=92t support all the stuff the older one did. But maybe that 

was

just for the beta release.



daniel



-----Original Message-----

From: H=E5kan Frennesson [mailto:hakan@c...]

Sent: Wednesday, September 12, 2001 3:45 PM

To: ASP Databases

Subject: [asp_databases] SV: Postscript to 'Server breaking Access DSNs'





Hi!



You might want to try this:

Delete your DSN, reboot and recreate it again.



Also make sure you have the latest drivers.



Hth,



Hakan



-----Ursprungligt meddelande-----

Fr=E5n: Marcus Hamilton [mailto:marcus@p...]

Skickat: den 12 september 2001 20:11

Till: ASP Databases

=C4mne: [asp_databases] Postscript to 'Server breaking Access DSNs'





Dear All,



This is a postscript to an earlier message that said:



I'm converting over to SQL Server 2000 from Access 97, but after having

installed SQL, none of my Access ODBC DSNs work.



The operating system I'm using is Windows Server 2000 Advanced.



I get the following error:



"Microsoft OLEDB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC

Driver Manager] Data source name not found and no default driver

specified."



I assuming that it is possible to run applications that use Access and

applications that use SQL Server on the same server.



The way that I'm trying to access the data in the script is:



set ors =3D Server.CreateObject("ADODB.Recordset")

ors.open "tableName","dsnName",adOpenKeyset,adLockOptimistic,adCmdTable





I have since discovered that whilst:



set ors =3D Server.CreateObject("ADODB.Recordset")

ors.open "tableName","dsnName",adOpenKeyset,adLockOptimistic,adCmdTable



does not work since installing SQL Server 2000



the following does:



set oConn =3D Server.CreateObject("ADODB.Connection")

oConn.open "dsnName"

set ors =3D oConn.Execute("SELECT fieldName FROM tableName")



The Recordset connection did work before SQL server was installed. I

can't change all of my connections to use the Connection object because

of legacy code.



Help would be much appreciated.



Regards



Marcus

Offhand I would change your connection string to "DSN=3D<name for your 

access

97 DSN>".



The DSN is only one of the properties that can be set in the connection

string (login, password etc). The connection string may be handled

differently for connections and recordsets, as a connections allow you 

to

specify login and password.



regards

David Cameron

nOw.b2b

dcameron@i...