Home » Infrastructure » Windows » Re: turned out to be ODBC driver related.
Re: turned out to be ODBC driver related. [message #99459] Mon, 19 November 2001 05:41 Go to next message
Sandy Lloyd
Messages: 1
Registered: November 2001
Junior Member
Jeff,

This is exactly the problem we have - but our applications use Oracle's ODBC driver. If we change to use Microsofts driver for Oracle, how do we construct the connection string?

Using:
Conn.open "DRIVER=Microsoft ODBC for ORACLE;User ID=IMS_LOGIN;PASSWORD=IMS_LOGIN;DATABASE=ASD;"

I get
Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[[Microsoft]][[ODBC Driver Manager]] Driver's SQLSetConnectAttr failed

Can you help please.

Sandy

----------------------------------------------------------------------
Re: turned out to be ODBC driver related. [message #99813 is a reply to message #99459] Wed, 10 April 2002 07:07 Go to previous message
Deepak
Messages: 111
Registered: December 1999
Senior Member
Try ging permissions to IUSR and IWAM accounts to Oracle root folder or OracleBIN folder. It tries to access some DLL's there and does not find the same. hence the problem.
Previous Topic: Re: What is the Database Startup Password for 8i Personal Ed.?
Next Topic: Installation Problems w/ Personal Oracle 8
Goto Forum:
  


Current Time: Fri Mar 29 02:53:01 CDT 2024