Re: 80004005 error with Oracle


"Darryl" <Darryl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F708EDF0-6235-4E5D-85A0-FB79168B1E0A@xxxxxxxxxxxxxxxx
I have a difficult problem with an Oracle connection that works in some
environments and not others.

I have developed a spread*** which uses VBA and ADO to get data from an
Oracle database. Development and testing worked fine, Development is on a
standalone PC. Testing and production usage is on Citrix Servers, and this
is
where the problem starts to come in.

On citrix1, the connection works exactly as required. On citrix2 and
citrix3, we get Run-time error 80004005. All three servers use the same
spread*** from a network drive and they all connect to the same Oracle
server. The only difference is the OS environment on each server, and I
have
located a difference in dll's. In development, I set up a Reference to the
ADO 2.5 Library, which translates to "msado15.dll". This functions exactly
the same way on citrix1, but when checking citrix2 and citrix 3, it
translated to "msado25.tlb". Further checking showed that citrix2 and
citrix3
had 2.5, 2.6, and 2.7 versions of the ADO Library. "msado15.dll" does
exist
on citrix2 and citrix3, but when I tried to reference it manually using
the
browse function, it would not connect because there was already a
reference
to 2.5 and the "msado15.dll" said it was 2.7! So much for backward
compatibility!

Has anybody had any experience with this where backward compatibility was
not actually backwardly compatible? I can't make the reference to 2.7 as I
can't guarantee that all the systems will have version installed.

Any suggestions?

Darryl


I believe the technical definition of your problem is called "Chewing on the
wrong animal."

The ADO Error 80004005 has many specific causes but they are all related to
an inability to make a "Connection". If you have installed the correct MDAC
for your platform then it is highly unlikely you are experiencing any
"backward compatibility" issues.

It is more likely you are experiencing a "permissions" problem either in
accessing Oracle or in accessing the COM components. Stop worrying about
MDAC and start looking at why your app can't "see" oracle.

hth
-ralph



.