Re: Late Binding

Thanks,

The code that uses ADO is necessary code.

I have looked at the component checker.

I take it that:

MDAC 2.1 - refers to ActiveX 2.1
MDAC 2.5 - refers to ActiveX 2.5
etc.

Is this correct?



"Tom Wickerath" wrote:

Is it safe to assume that 2.1 or higher
would be on Office 2000 und up installations.

In general, this should be a pretty good assumption, since the ADO 2.1
library is added by default to all new databases created using Access 2000.
However, where is your compile error when you remove a reference to ADO
totally? If it is in old code that you are no longer using, then you might be
better off to just comment out (or remove) that code. If it turns out that
you really do need a reference to this library, I'd suggest becoming familiar
with the MDAC Component Checker utility, because you will undoubtedly come
across one or more PCs with some type of configuration problem. The symptoms
include everything working fine on all other PCs, but not on the affected PCs.

Component Checker: Diagnose problems and reconfigure MDAC installations
http://support.microsoft.com/kb/307255


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

"tmort" wrote:

I tried to recompile without an ActiveX reference and it didn't work. I see
I am using adodb.

It will compile with ActiveX 2.1 (although I haven't checked functionality
yet) I see that what libraries are available are dependent on a number of
things including service packs. Is it safe to assume that 2.1 or higher
would be on Office 2000 und up installations.

Would you suggest this approach?

Thanks
.

Relevant Pages

  • Re: Distributing MDAC with VB Application
    ... using both DAO and ADO in your project is to be SURE to qualify object names ... > Is there something else I need to include if using MDAC 2.5 or higher? ... include the Jet components ADO requires. ... you might have to distribute the Jet Components installer. ...
    (microsoft.public.vb.winapi)
  • Re: Recommended data access model
    ... This is from MDAC 2.8 SDK. ... "The Role of ADO in MDAC ... The Microsoft Data Access Components provide data access that is ... easy-to-use interface to OLE DB. ...
    (comp.databases.ms-access)
  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.vb.database)
  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.vb.database.ado)
  • Re: MDAC question
    ... > The application server runs VB6 code. ... > decided to check the MDAC versions on my two physical servers. ... the ADO Data library are your applications using? ... not the cause since ConnectionRead is called by drivers and providers. ...
    (microsoft.public.vb.general.discussion)