Re: problems with ODBC to Oracle 8.1.5

The 8i client is not supported by Microsoft. Support will be added in the future, but for now you must use the 8.0.5.x or prior client when working with the Microsoft client stack.

As to ODBC vs. OLE DB with ADO - under load in a multithreaded  client, the ODBC driver (via the OLE DB Provider for ODBC) still provides both better performance and stability than the OLE DB provider. For traditional client/ server architectures, both provide roughly the same behavioral characteristics.

Mike

"Ray Porter" <ray_porter_at_unc.edu> wrote in message news:8csh8q$8$1_at_news2.isis.unc.edu...
> Thanks for the reply.
>
> "K Stahl" <BlueSax_at_Unforgetable.com> wrote in message
> news:38EDFE33.899408BA_at_Unforgetable.com...
> >
> > 1. Don't use odbc if you are using ADO. Use OLEDB.
>
> I will be using ADO from an in-house developed application. The end users
> still need ODBC to connect with MS Access for ad hoc queries.
>
> > 2. Make sure that tnsnames.ora is set up correctly. It would be nice if
 you
> > can install the Oracle client tools on your PC (e.g. sqlplus) so that
 you
> > can make sure that sqlnet is working properly.
>
> SQLPlus is installed and connects to the database with no problem. I've
> also now installed the Oracle supplied ODBC driver and have successfully
> connected using it. My problem is only with the MS supplied Oracle ODBC
> driver that comes with MDAC 2.5.
>
>
> --
> ================================================
> Ray Porter
> Applications Analyst Programmer
> Administrative Information Services, UNC-CH
> Phone: 966-5878
> email: ray_porter_at_unc.edu
> dragon_at_email.unc.edu
> Home Page: http://www.unc.edu/~dragon/
>
> "Meddle not in the affairs of dragons,
> for thou art crunchy and taste good with ketchup."
>
>
>
Received on Sun Apr 16 2000 - 00:00:00 CDT