Please note that this break only happens when the application is re-compiled. This change causes a break that if your application is re-compiled on Windows 7 SP1 and it uses early binding to ADO, it probably doesn't work on down-level OSes, such as Windows 7 RTM, Vista, etc. The interfaces with new GUIDs (in Windows 7 SP1) don't have such issue. Therefore, you receive a 'Type Mismatch' error message when you try to run the macro.' However, applications that use these APIs still use the LONG data type. On 64-bit versions of Windows, these ADO APIs process arguments by using a 64-bit data type (such as the LONGLONG data type). 'Some ADO APIs are platform dependent in ADO 2.7 and later versions. The reason of this change is mentioned in KB983246():
There is a by design change in ADO in Windows 7 SP1 that interfaces have new GUIDs. If you want to upgrade Windows XP to the MDAC 2.7 SP1 Refresh (.2), you must upgrade Windows XP to Windows XP SP1, and then you must apply SQL Server 2000 SP3a (MSDE 2000 SP3a).
#Mdac version 2.8 install#
If you want to upgrade Windows XP to the original release of MDAC 2.7 SP1 (.9), you must install the Windows XP SP1 release. On a computer with Windows 7 SP1 installed, you develop and build your application that is using ADO for database access, you find the application doesn't run on the Windows XP, Windows Vista, Windows 7 without SP1. Essentially you have to hand edit the STF file for VS6 Service Pack 5 to skip the MDAC check. Found a solution to this that actually works well. Though this isn't supported and you get the normal warnings about maybe not working on Windows 7, but i now have it installed and compiling. If you try to run the MDAC 2.6 Mdactyp.exe file or the MDAC 2.7 Mdactyp.exe file on Windows XP, the process appears to complete successfully, and a successful installation of the MDAC components is reported. Microsoft Security Bulletin MS11-002 - Critical Vulnerabilities in Microsoft Data Access. The latest updates involving MDAC I can find is.
#Mdac version 2.8 update#
I guess the user's computer needs to install an MDAC update that has yet to be released for platforms other than Windows 7.