adodb.dll

  • Thread starter Thread starter David Cui
  • Start date Start date
D

David Cui

Hi!

I have a adodb.dll in GAC and C:\Program Files\Microsoft.NET\Primary Interop
Assemblies.
I have a dll written in vb6, let us call it a.dll. a.dll
uses mdac 2.1. I run tlbimp against it, on some of
the machines, it will use the adodb.dll in the GAC.
However, on some of the machines, it will create
a new adodb.dll which is a interop of msado21.tlb.

How can I make them all use the adodb.dll
in the GAC?

Thanks.
 
¤ Hi!
¤
¤ I have a adodb.dll in GAC and C:\Program Files\Microsoft.NET\Primary Interop
¤ Assemblies.
¤ I have a dll written in vb6, let us call it a.dll. a.dll
¤ uses mdac 2.1. I run tlbimp against it, on some of
¤ the machines, it will use the adodb.dll in the GAC.
¤ However, on some of the machines, it will create
¤ a new adodb.dll which is a interop of msado21.tlb.
¤
¤ How can I make them all use the adodb.dll
¤ in the GAC?

See if the following helps:

INFO: Using the Primary Interop Assembly for ADO (ADODB) in Visual Studio .NET
http://support.microsoft.com/default.aspx?scid=kb;EN-US;318559


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Paul,

Thank you for your help.
I added the reference to the adodb.dll using the way described in Q318559.
But once I build my project,
ide will automatically add a new reference ADODB1 which is an interop of
msado21.tlb.

:-(
 
¤ Paul,
¤
¤ Thank you for your help.
¤ I added the reference to the adodb.dll using the way described in Q318559.
¤ But once I build my project,
¤ ide will automatically add a new reference ADODB1 which is an interop of
¤ msado21.tlb.

Not sure exactly what might happening although running the tlbimp utility against a previous version
of ADO might be causing .NET to use the older version of MDAC.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top