> I had identical configurations on both NT Server 4 and
> Windows 2000 AS - as Dave says - installing CF 4.01 on
> Win2K breaks MDAC 2.5 to the point where some ODBC
> instructions won't work anymore, and it seems to destroy the
> SQLOLEDB provider almost completely.
>
> I certainly won't be upgrading my Win2K until I have to for
> the sake of CF 4.01 Enterprise, but I do expect Allaire to
> fix what I regard as a very serious bug.
>
> I don't think Allaire should provide and install MDAC anyway
> with the install - MDAC is a matter for system administrators
> to manage on their own setups as they see fit IMO.
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.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
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.
