AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
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 doesnt care one way or the other.It seems strange to go from 2.8 to 6.0.
There is also a Microsoft ActiveX Data Objects Recordset 6.0 Library reference. Im confused, does it have to do with VS 2005.NET any information will be appreciated, thanks. Outlook Global Address List API Viewer utility.NET API Viewer Utility System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24 LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6. Should I use 6.0 even though this app will be running on Vista and Non Vista machine. I think Ill stick with 2.8 since there was no functional gains listed. Beginning with about SP2 of Windows 2000 MDAC became a part of Windows, not an optional installable item. Beginning with MDAC 2.5 a new strategy started in an attmpt to relieve a bit of DLL Hell. 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. Microsoft Activex Data Objects 6 Library Series Of TypelibsIn order for old programs compiled referencing earlier MDAC releases to keep running, a series of typelibs is installed. You get one for ADO 2.0, one for ADO 2.1, one for ADO 2.5, etc. MDAC installed). All of these TLBs point to msado15.dll and each has the subset of class IDs supported in the MDAC release it matches. 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. 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. I.e. 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. Windows 2000 introduced System File Protection to keep rogue installers from trashing critical system files. This became more mature in Windows XP Gold, and still more mature in Windows XP SP2. 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. With the release of Vista SFP was renamed Windows File Protection, was made even more robust, covers many more system files. 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. Typelibs are included covering ADO 2.0, 2.1, 2.5, 2.6, 2.7, and 2.8 interfaces so old programs still work. 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. 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 couldnt be expected to work anyway. There is no longer an ADOR 2.0 or 2.1 library, just typelibs pointing into msado15.dll. ADOX must be treated as a special case. For some reason ADOX was never moved to this new versioning system based on external typelibs. If you develop a program on XP that uses ADOX you might have been tempted to set a reference to ADOX 2.6 since thats the only typelib VB can locate. DO NOT DO THIS. In Vista there is no ADOX 2.6, and no redirection typelib to allow your program to match intefaces with Vistas ADOX 6.0 Instead you need to use late binding with ADOX, or else sacrifice portability to Windows 2000 and Vista.
0 Comments
Read More
Leave a Reply. |