----- Original Message -----
From: Dave Watts <[EMAIL PROTECTED]>
Sent: 07 April 2000 23:24
Subject: RE: 4.01 and 2000
>
> CF 4.5.1 RTM doesn't break MDAC on Win2K. In any case, it's a very simple
> process to fix the problem with earlier versions; it's just a little
> tedious. Lots of applications, not just CF, will modify some or all MDAC
> parts; SQL Server 7, for example, forces MDAC 2.0, because it won't work
> with earlier versions. Microsoft, on the other hand, changed how MDAC
> upgrades are handled in Win2K, which is the bigger problem from a
> compatibility standpoint. MDAC in Win2K isn't a separate component, but part
> of the OS, which means that you won't be able to install new MDACs, but will
> change MDAC through Win2K service packs and updates.
I have never known a higher MDAC level be physically downgraded to a lower MDAC
level - AFAIK M$ do version checking on these things. I recent example is NT
MDAC 2.5 RTM where SQL Server 7 SP2 has, I believe (I haven't checked) a higher
level SQL ODBC driver included. This leads me to believe that CF 4.01 was doing
something more fundamental - on a machine with the highest level MDAC it tried
to do something which plain broke it.
The point I am making is that I don't think Allaire should include MDAC in the
install at all - they should simply state the minimum server requirements for
any given version of CF as they do for other hardware and software, and state
minimum levels of MDAC required if necessary - it is up to the system
adminstrator then to comply. This is particularly true of Win2k install, where,
as you say, MDAC is a fundamental part of the O/S installation.
Adrian Cooper.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
