- #MICROSOFT ACTIVEX DOWNLOAD HOW TO#
- #MICROSOFT ACTIVEX DOWNLOAD UPDATE#
- #MICROSOFT ACTIVEX DOWNLOAD SERIES#
- #MICROSOFT ACTIVEX DOWNLOAD DOWNLOAD#
These include named parameters (ADO 2.6) and some things specfic to late versions of SQL Server.
#MICROSOFT ACTIVEX DOWNLOAD HOW TO#
Some of this is covered in The MDAC 2.5 Stack and Windows File Protection and Windows Data Access Components SDK Overview.Ī little more is covered in How To Develop with ADO Version 2.5 or Later and Install on ADO Version 2.0 and other KB articles.įor greatest portability set a reference to ADO 2.5 in VB6 unless you need features introduced in ADO 2.6 or later. If a Win9x system has MDAC 2.5 or later installed late bound programs should work there too, but since anything older than Win2K SP4 is now unsupported Microsoft doesn't care one way or the other. In Vista there is no ADOX 2.6, and no "redirection typelib" to allow your program to match intefaces with Vista's ADOX 6.0! Instead you need to use late binding with ADOX, or else sacrifice portability to Windows 2000 and Vista. If you develop a program on XP that uses ADOX you might have been tempted to set a reference to ADOX 2.6 since that's the only typelib VB can locate. There is no longer an ADOR 2.0 or 2.1 library, just typelibs pointing into msado15.dll.įor some reason ADOX was never moved to this new versioning system based on external typelibs. By MDAC 2.8 the whole package was tailored to each Windows OS anyway, and since there is no MDAC 2.8 for Vista it couldn't be expected to work anyway.ĪDOR was folded in the same way. WFP is so robust now that if you try to install MDAC 2.8 into Vista it just chuckles to itself, lets you think something installed, and ignores the whole thing. Typelibs are included covering ADO 2.0, 2.1, 2.5, 2.6, 2.7, and 2.8 interfaces so old programs still work. Vista also changed a very late MDAC 2.8 and renamed it Windows DAC 6.0 to emphasize that it is part of Windows, not something for users to muck about with and try to install over. and cannot be turned off at all in Vista itself. With the release of Vista SFP was renamed Windows File Protection, was made even more robust, covers many more system files.
#MICROSOFT ACTIVEX DOWNLOAD UPDATE#
At this point it covers (protects) MDAC components as well, and they can never be replaced except through a Windows Update MSI as long as SFP is turned on. This became more mature in Windows XP Gold, and still more mature in Windows XP SP2. Windows 2000 introduced System File Protection to keep rogue installers from trashing critical system files. your program cannot use features that were new in ADO 2.6, 2.7, or 2.8 even though it is really using the ADO 2.8 library. However it actually uses msado15.dll which is the MDAC 2.8 version but is limited to the interfaces supported by the MDAC 2.5 version of ADO. So if you have MDAC 2.8 installed in Windows XP your program can be compiled against the ADO 2.5 typelib and it will work. All of these TLBs point to msado15.dll and each has the subset of class IDs supported in the MDAC release it matches. You get one for ADO 2.0, one for ADO 2.1, one for ADO 2.5, etc.
#MICROSOFT ACTIVEX DOWNLOAD SERIES#
In order for old programs compiled referencing earlier MDAC releases to keep running, a series of typelibs is installed. The newest ADO on your system is always named msado15.dll, which is not ADO 1.5 but instead it is the newest version (and only version) installed. At that time updates to MDAC were really Windows updates.īeginning with MDAC 2.5 a new strategy started in an attmpt to relieve a bit of DLL Hell.
#MICROSOFT ACTIVEX DOWNLOAD DOWNLOAD#
You cannot download 6.0 for installation in a pre-6.0 version of Windows (Vista is Windows 6.0).īeginning with about SP2 of Windows 2000 MDAC became a part of Windows, not an optional installable item. MDAC 2.8 will not install into Vista though it may let you think it did.