#ROOTSMAGIC 7 WONT COMPLETE CONVERTING HOW TO#
#ROOTSMAGIC 7 WONT COMPLETE CONVERTING INSTALL#
#ROOTSMAGIC 7 WONT COMPLETE CONVERTING CODE#
#ROOTSMAGIC 7 WONT COMPLETE CONVERTING WINDOWS 8#

This can save everyone time and effort to browse through your Please reply or discuss on the new forum thread instead of this one. [ Important Note: Since this thread become very long and it is ineffective to do more communication on this thread, I have opened a new forum thread at: Your feedback is very important to the success

#ROOTSMAGIC 7 WONT COMPLETE CONVERTING WINDOWS 8#

Report any new (un-addressed) issues to us, so that we can address them in the Windows 8 RTM build. So, I hope everyone who has impacted by this issue to try out the Windows 8 Preview build as soon as possible. This forum post does not implyĪny future support of these out-of-support technologies.]

NET ADO interop are not supported anymore.

#ROOTSMAGIC 7 WONT COMPLETE CONVERTING HOW TO#

To downlevel, in order to obtain the backward compatibility behavior (see the Visual Studio setting for more detail on how to target downlevel platforms) [Please note that VB6 and. If you are using C++ and using 'include header method', you have to use the latest Win8 SDK and target your applications

#ROOTSMAGIC 7 WONT COMPLETE CONVERTING CODE#

Using 'import msado15.dll', you have to change the reference to 'msado60.tlb' in your code and recompile to get downlevel platform compatibility. NET) are referencing the 6.0 (or below) typelib, you can simply recompile your application on the Windows 8 Preview build and then your application should now work on downlevel platforms as well. The downlevel support requirement are gone in the future (say, those downlevel platforms are not relevant anymore as times goes on), customers should seriously consider to migrate to the 6.1 typelib, which is the only supported typelib in the future. With the newly-implemented solution, if customers require downlevel support, they should compile their applications with the 6.0 typelib (or 2.x typelib). COM+ marshalling scenario (as reported in the forum thread: (Actually, ADOR is simply a subset of ADO) btw, customers are advised to migrate to ADO interfaces. Since this binary is deprecated, there is no new interfaces introduced for ADOR. msadoR15.dll has been reverted back to what it looks like in Win7 RTM. We also fixed the thread handle leak issue in ADO Async execution mode (as reported in the forum thread: You are advised to migrate to the 6.1 typelib whenever there is no more downlevel support concern for your applications. Therefore, the 2.x and 6.0 typelib are used for backward compatible purpose, and the 6.1 typelib is used for 64-bit VBA solutions. Revert back all 2.x typelibs to what they looked likeĪs in Win7 RTM. Ship a new 6.1 typelib (which contains both new and deprecated interfaces) and embed it inside the msado15.dll. Pull out the 6.0 typelib from Win7 RTM and ship it via the new typelib file: msado60.tlb. In the preview build, what we have done are:

#ROOTSMAGIC 7 WONT COMPLETE CONVERTING INSTALL#

Please note that there is no customer support if you got any problem with the Windows 8 Preview build - so please only install the build on your test machines, but not your business-important machines). Please download the Preview build freely at: The Windows 8 Preview build contains the complete fix of this issue. Set cn = o ' this errors when compiled on Win 7 SP1 and run on older versions of Windows due to the changed IID of the dispinterface _Connection Set o = CreateObject('ADODB.Connection') ' this does still work To verify the error you can use code like this in VB6 or equivalent in VB.Net or C# and compile it on Win7 SP1 and run it on Win7 RTM or older versions of Windows: Dim cn As ADODB.Connection I really hope I am missing something as this change seems to be a massively breaking change in the MDAC API. The CLSIDs still match, so the COM objects get created but due to different IIDs they cannot be used.

That means that all code produced on Windows 7 SP1 using ADODB cannot be run on any other version of Windows as the IIDs differ. I hunted this down to changed Interface IDs in the msadoxx.tlb files. After I installed Service Pack 1 on my Windows 7 圆4 Ultimate my applications which use MDAC 2.8 COM components for database access do not work on other Windows versions any more.

Rootsmagic 7 wont complete converting