ADO Connection Error
Posted in 2000
Topics: Connectivity: ODBC / JDBC / .NET, Security, Permissions & Auditing
I am trying to convert from DAO to ADO, and I'm having trouble connecting to the DB. The environment is VB6, on an NT V4.0 client, using ODBC and Informix 2.8 in a DSN, to connect to an Informix DB on a SCO-UNIX server. When I try to connect, I get a "Driver's SQLSetConnectAttr failed" error. When I use the VB control to try to connect, I get a "catastrophic error". Is there somewhere I can look to find possible reasons for these errors? Has anyone out there run into this before, and found a way around it? The Errors collection only has the SQLSetConnectAttr error in it. If I try a UID/Password that is invalid, I get an error indicating such, so it looks to me like it's getting to the DB and trying to make the connection. Any help would be greatly appreciated. Thanks, Joel Sent via Deja.com http://www.deja.com/ Before you buy.
>Subject: ADO Connection Error >From: jwz1@my-deja.com >Date: 20.03.00 02:06 W. Europe Standard Time >Message-id: <8b3tib$cb9$1@nnrp1.deja.com> > >I am trying to convert from DAO to ADO, and I'm having trouble >connecting to the DB. The environment is VB6, on an NT V4.0 client, >using ODBC and Informix 2.8 in a DSN, to connect to an Informix DB on a >SCO-UNIX server. When I try to connect, I get a "Driver's >SQLSetConnectAttr failed" error. When I use the VB control to try to >connect, I get a "catastrophic error". > >Is there somewhere I can look to find possible reasons for these >errors? Has anyone out there run into this before, and found a way >around it? > >The Errors collection only has the SQLSetConnectAttr error in it. If I >try a UID/Password that is invalid, I get an error indicating such, so >it looks to me like it's getting to the DB and trying to make the >connection. > >Any help would be greatly appreciated. > >Thanks, > >Joel > > >Sent via Deja.com http://www.deja.com/ >Before you buy. > > > > > > Install Client SDK 2.40 and try the 3.31 driver. Also test the driver with ODBC SDK 3.5 if the problem persists. Nona