RE: MDAC Versioning

Tech-Archive recommends: Fix windows errors by optimizing your registry

I've resolved the issue. The dasetup.exe program works if you supply the /u
switch (to initiate an MDAC rollback). If you provide any other switch or no
switch you get the fatal error loading EULA file message. Once the rollback
completed, re-installing mdac sorted the issues out.


"SpodgyTwoSugars" wrote:

> I've just spotted Frank Houston's post on a similar issue. The last machine I
> had this issue with, I attempted to install 2.8 direct from Microsoft and the
> dlls wouldn't overwrite. I don't think the errors on the MS hotfix page apply.
>
> The machine having problems is win XP/Off XP.
>
>
> "SpodgyTwoSugars" wrote:
>
> > Hi,
> >
> > I administer several Access/SQL Server databases for a hospital Trust, that
> > use a combination of ODBC linked tables and ADO.
> >
> > MDAC has proved to be an occasional bugbear, as sometimes the dlls don't
> > work correctly and a database will produce errors like "Open Method of
> > connection failed" and "Provider cannot be found". The typical solution for
> > this is to install a later version of MDAC.
> >
> > The problem is, if the version on the machine is the same as being installed
> > (typically 2.7 or 2.8) then the setup program will not overwrite the dlls. I
> > used to be able to get round this by running the dasetup.exe program to roll
> > MDAC back and then reinstall. Lately, I can't do this as I keep getting
> > "Fatal Error Loading EULA file" while attempting to run dasetup. I have
> > suspicions that something has been installed on the network which is
> > preventing the program working.
> >
> > The component checker isn't proving helpful, as this only provides an
> > inventory of the dlls.
> >
> > Does anyone have either of the following solutions :
> >
> > 1) A remedy for the EULA file error or possible path of investigation?
> > 2) Another method of forcing MDAC to reinstall over the current version?
> >
> > Thanks in Advance
> > Jim
> >
.

Quantcast