Yes, ORACLE for NT, needs to be installed on the web/application server. And you will need to set up a db alias pointing to the ORACLE db.<BR><BR>Then the connections String is something like ...<BR><BR>DRIVER=Microsoft ODBC for Oracle;UID=UserID;PWD=Password;SERVER=dbAlias;<BR> <BR><BR>HTH<BR><BR>Jerry
Jerry -<BR><BR>Just curious ... I was testing some things using ASP->Oracle DB and am using a clients 95 machine w/PWS.<BR><BR>I made an ODBC connection using Oracle 73 v2.5 drivers. I then used the connect string <BR><BR>objConn.ConnectionString = "DSN=<dsn_name>;UID=<uid_name> ;PWD=<pwd>"<BR><BR>It works fine? I thought the provider=, server= or driver= would have been necessary? Would the above string work in your environment? <BR><BR>Just looking for some insight to avoid problems later.<BR><BR>Thanks.
Yes, but we use the other method, which is comparable to a DSNless connection to an Access DB. We do this because our production web / db servers are located halfway across the country.<BR><BR>HTH<BR><BR>Jerry
This is exactly what I am planning to do... How does the server know what database you are referring to? This line does not use a database name or alias...? Is this something set up through SQL net...which I understand needs to be installed first.<BR><BR>Thanks,<BR>Tim Silva<BR>email@example.com<BR>timsilva@j ps.net