make a new library with the same file name but that implements all of the older interfaces and then you provide separate. or else you do as was done with ADO later on, i.e.
Normally you are supposed to make a new library (with a new file name) much as ADO did in its early revisions. When you break binary compatibility like this it can have serious consequences such as those we're seeing described here.
It sounds like the IE10 install copies over the 2.0 libraries with 2.1 libraries but fails to properly unregister the old 2.0 interfaces or register the new 2.1 interfaces in the process.
I assume this is leftover registration from the original libraries. Still others are seeing no problems at all even with IE10 installed.Īccording to those giant screenshots above the two libraries shown there seem to be registered, but with the original (2.0) interfaces. Others claim uninstalling IE10 makes IDE development work again. Some say previously built programs still run Ok. And from the posts made here I'm not sure we know when this problem occurs and when it doesn't. There doesn't seem to be anything authoritative to tell us what's going on. It also seems as if anyone who gets the new version registered and compiles against it will produce applications that won't work on pre-IE10 systems (Win7, Viasta, XP, and on down). They can't just tell users they have to uninstall IE10 to run their programs. IE10 can't be resisted forever, IE9 has some serious problems.įor another they need to worry about Win7 as a deployment target in the wild.
This is still an issue for any serious VB6 developer.įor one thing eventually they'll have to move off Vista which is the last version of Windows Microsoft ever said supported VB6 development. This project was previously compiled and distributed online so unless I can solve this problem I guess there won't be any future updates.
I could try system restore but I have no idea what update may have caused the problem and my restore points only go back about 20 days. Object=#2.0#0 mscomctl.ocxīut I'm not able to tell if the project file is referencing the proper version of the control. If I edit the project file (of the project that no longer loads) with notepad the reference to mscomctl is: Opened a new project in VB6 and tried to add Microsoft Windows Common Controls 6.0 (SP6) butĪs soon as I click "Apply" I still get the error "object library not registered" Re-Registered using the command "regsvr32 mscomctl.ocx" (successful)ĥ. Unregistered the control using the command "regsvr32 /U mscomctl.ocx" (successful)Ĥ. I changed directory to C:\Windows\SysWOW64ģ. Opened a command prompt (run as administrator)Ģ. ocx file.īased on other posts regarding this problem here is what I've tried so far.
I'm wondering if some recent program installation or windows update has caused this problem by updating the. The file date/time stamp is: 1,046 KB 8:58 PM. The control causing the problem is Microsoft Windows Common Controls 6.0 (SP6) mscomctl.ocx. When I try to load it I'm now getting the error message "object library not registered". For some reason I am no longer able to open my current project in VB6.