Re: Can't connect to Oracle using MSDAORA OLE DB provider

Syarzhuk wrote:

> Walter T Rejuney <BlueSax_at_Unforgetable.com> wrote:
> >You said that you had to reinstall everything from scratch. Does that mean you also reinstalled the mdac?
>
> Yes. As I said, we can connect using Oracle OLE DB provider, but for some
> reason MSDAORA cannot be initialized
>
> >If not, give that a try because that is where the MSDAORA provider is installed.
>
> Understood. MDAC is installed. MSDAORA is installed (C:\Program Files\Common
> Files\System\ole db\msdaora.dll)
>
> Originally we had 2.5 installed. Then we decided to try to go back to 2.1
>
> >As far as I have ever heard, it is not possible to back out of an MDAC upgrade to go to a previous version
> >since the installer will simply report success even though it doesn't do any work because it will not overwrite
> >older files.
>
> That's what I thought. Anyway we gave it a try and now VB shows 2.1 in the
> References dialog so I assume it did overwrite - very surprising to me.
>
> >Is there some reason that you need the older version of the mdac?
> No, other than the <subj>
>
> >The current version is 2.6
> And it didn't work for us
>
> Anyway, I guess I need to clarify my question: what does MSDAORA.DLL need to
> "initialize provider"? -- Belarusan Music Source - http://www.belmusic.net
> Byvajce zdarovy, zhyvice bagata Be healthy, stay wealthy

That part is easy to explain. If you are using ADO and the MSDAORA.DLL then you are using OLE DB. The basis for OLE DB is a provider. To make a connection, the provider must be initialized. However, this doesn't explain why this isn't working for you.

Can you show your object definitions and your connect string? Received on Mon Dec 18 2000 - 07:59:10 CST