Problems with multiple versions of Oracle client installed

[Andrew Shepherd]

(I'd inadvertently posted this to the ASP page, not the ADO page. This
should be the right newsgroup now)


In my company there is one data repository on an Oracle 9i database,
and another on Oracle 10g. To be able to process the Oracle 10g
database, I had the Oracle 10g client installed on my machine.


Now a .NET application that was reading the Oracle 9i database has
stopped working.


I have not uninstalled the Oracle 9i client. I was also separately
viewing the Oracle 9i data via Microsoft Access, and am still able to
do so.


My assumption is that .NET is trying to access the database using the
latest client driver. Is there any way to tell it to use version 9i?


I might try creating an Access database that links to the Oracle
database, and making my .NET app talk to the Access database. Only that

feels too much like an act of desperation, and I can't help thinking
there'd be a more elegant solution.

 

[Andrew Shepherd]

I resorted to a convoluted workaround:

I created a new Microsoft Access database that links to the relevant
Oracle database tables via ODBC.

Now my .NET application uses the Jet OleDB provider to talk to the
Access database which reads the ODBC datasource.


In this instance neither performance nor maintainability is a priority.
However, I'm still interested to know if there was a simpler solution.