Microsoft ODBC driver issue

[Pinbee]

I'm not sure if this is the correct site to post this
question...worth a try. Hope someone will be able to shed
some light on the issue I have...I've been searching for
an answer for so long but came up with nothing that can
be of help.

In my winxp, I cannot run the application that uses
Microsoft ODBC for Oracle driver once I installed another
application that uses Oracle in Orahome90 driver.
The 'Connection to database failed error' will be
displayed when launching the first application.

However, if I change the first application to use Oracle
in Orahome90 driver, both application will work.

Is there any known problem between the two drivers?
Because the fix I made is not allowed. I'm told to keep
the Microsoft ODBC for Oracle driver and change the other
driver instead. Is this possible?

What files could possibly be overwritten that's causing
this problem?

Please advise.

 

[Rob Schneider]

I'm not sure if this is the correct site to post this
question...worth a try. Hope someone will be able to shed
some light on the issue I have...I've been searching for
an answer for so long but came up with nothing that can
be of help.

In my winxp, I cannot run the application that uses
Microsoft ODBC for Oracle driver once I installed another
application that uses Oracle in Orahome90 driver.
The 'Connection to database failed error' will be
displayed when launching the first application.

However, if I change the first application to use Oracle
in Orahome90 driver, both application will work.

Is there any known problem between the two drivers?
Because the fix I made is not allowed. I'm told to keep
the Microsoft ODBC for Oracle driver and change the other
driver instead. Is this possible?

What files could possibly be overwritten that's causing
this problem?

Please advise.

Sounds like the Microsoft-supplied driver for Oracle is buggy and the
other one (you don't say source) is not buggy. Microsoft ODBC drivers,
especially for non-Microsoft drivers, are not typically the best quality
compared with others.

It is not possible for you to change the other driver. The driver is
what it is. You may wish to look at the information about the dirver
(via the ODBC menus) for vendor, version, etc.

Your choice is to
- spend time and money working with the developers of the "other"
application that successfully uses the non-buggy software to find out
how to make their product work with the buggy Microsoft ODBC driver. My
hunch is they will resist this and tell you either it's "not possible"
or something they have no interest in given that their product works
with the driver they provided you.
- Or, you can spend time and money convincing those who won't allow you
to use the non-buggy software to use it. Find out *specifically* why
they do not allow the other the other driver.

Presumably you are business. Base the course of action on economics.