Re: ADO Version Overview



> I am confused about the various MDAC versions. On My server there seem to
be
> many versions from 2.1 to 2.8 are all of these avalivle for use?

What makes you think there are multiple versions installed on your server?

> Or as a
> newer one is installed it is the one that interacts with the application
such
> as and aspx page getting data from SQL Server?
>
> Is the a tool to manage or remove older versions?

I don't think the older versions are installed. ADO object are COM objects
and each successive version of MDAC is backwardly compatible with the older
versions. The result is that if you had an App that was compiled with MDAC
2.5, and it needed to open a 2.5 Recordset, that is no problem even if MDAC
2.8 is installed. A 2.8 Recordset exposes a 2.5 Recordset interface (and all
previous Recordset interfaces) and it is the 2.5 interface that the App uses
(of the 2.8 Recordset). The same is true for Connection & Command objects.

> Is there a way to tell which ones are being used?

See above.

> Is there a way to determine what Providers are in specific MDAC versions?

AFAIK, the providers that come with MDAC are

Microsoft provider for Oracle
Microsoft provider for SQL Server
Microsoft provider for ODBC drivers

That is it

For Microsoft Jet 4.0 provider (for Access) you have download separtely

Stephen Howe



.



Relevant Pages

  • [NT] Unchecked Buffer in MDAC Function Could Enable SQL Server Compromise
    ... A security vulnerability results because the MDAC functions ... SQL Server service to take actions dictated by the attacker. ...
    (Securiteam)
  • RE: vb6 app no longer connects to Access DB on Term Server 2003
    ... The trick was to re-install the appropriate MDAC in a very funky way... ... your version of Windows to a temporary folder. ... we recently upgraded the Terminal Server from the 2000 version to ... -2147024769 Automation Error The specified procedure could not be found ...
    (microsoft.public.access.modulesdaovba)
  • 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)
  • 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.data.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.database)