Which MDAC Version to Install

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm running VB6 Enterprise on Windows Me. My MDAC somehow got hosed, so I'm
planning on using Component Checker with the /D parameter to remove the two
versions that I currently have parts of, i.e. 2.7 and 2.1.3513.2

The dilemna I have is that VB6 Enterprise includes MDAC 2.0 on the CD;
however, downloading from online you have to chose from 2.6 thru 2.8. What
would be my best course of action? First of all, I want recordsets in my
VB6 to work again; and secondly, when I distribute my software, I want it to
now blow up due to the version being too new for some older MDACs that might
be out there.

Thanks.


.

Relevant Pages

  • Re: Which MDAC Version to Install
    ... I'd install the latest MDAC 2.8 SP1. ... 'Microsoft ActiveX Data Objects 2.x Library' ... Microsoft MVP [Windows] ... | The dilemna I have is that VB6 Enterprise includes MDAC 2.0 on the CD; ...
    (microsoft.public.data.ado)
  • Re: Publisher catelog merge- cannot open data source file
    ... Take a look at your MDAC components. ... MDAC Utility: Component Checker ... outlook message earlier today, but deleted the field I copied before the ... engine failures" error message when you try to perform a mail merge by ...
    (microsoft.public.publisher)
  • Re: Late Binding
    ... The code that uses ADO is necessary code. ... I have looked at the component checker. ... MDAC 2.1 - refers to ActiveX 2.1 ...
    (microsoft.public.access.queries)
  • RE: MDAC 2.8 uninstall
    ... Have you tried to run the Component Checker from the run line with the /d ... to uninstall mdac and install the version you specified. ... the /NR switch along with the /d switch it will not install what ever mdac ...
    (microsoft.public.win2000.setup_deployment)
  • Re: missing DTS connections
    ... I ran the component checker and it reports that MDAC is OK! ... >>All of us have missing connections in the DTS designer. ... >>installation all the connections were available however after applying ...
    (microsoft.public.sqlserver.connect)