RE: Roll back MDAC to version 2.5
- From: SpodgyTwoSugars <SpodgyTwoSugars@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Apr 2005 03:06:02 -0700
I've had a slightly different problem on a similar theme.
I roll Access frontend/SQL Server Databases out across a network to a large
number of machines. Occasionally the ADO dlls fowl up so I need to run MDAC
to fix them. If the host machine was running 2.5, fixing the dlls was
relatively simple because you could install 2.7 over the top.
If the machine encountered a problem, and MDAC was at 2.7, this presented a
problem, because the installation program would not overwrite the dlls
because they were the same version. After several months of frustration, I
stumbled across the dasetup program in the c:\program files\microsoft
shared\dasetup folder.
This program allowed the system to rollback to the previous version of mdac.
It was then a simple case of installing 2.7 again and problem solved.
Recently however something has changed on our network. No matter which
machine I'm adminstering, when I try to run dasetup I now get the message
"Fatal Error Loading EULA File" and the program halts. Assuming the machines
are a mixture of Windows 2000/XP, Office 97/XP, and that my user profile has
full administration rights, has anyone any ideas of what I could investigate,
or the source of this problem?
.
- References:
- Roll back MDAC to version 2.5
- From: Elliott
- RE: Roll back MDAC to version 2.5
- From: Anton Klimov [MS]
- Roll back MDAC to version 2.5
- Prev by Date: Re: SQLConnect
- Next by Date: changing lanugae of odbc datasource dialog
- Previous by thread: RE: Roll back MDAC to version 2.5
- Next by thread: vista que devuelva el mas nuevo registro de cada cliente segun determinados valores
- Index(es):
Relevant Pages
|