The ADO issue was fixed in Windows 8.x and later but since Win7 is in extended support it never had a fix pushed out. This is a lot like the mess they made of ADO in Win7 SP1, and these are reasons why Win7 should not be used as a development platform. I suspect that the Office Team owns mscomctl.ocx these days and they broke compatibility either out of ignorance or because they just didn't care. When you have different Interfaces the ProgID may be the same but different PE files would (or should) exist but they'd have varying ClsID values.Īt some point not to long ago Microsoft broke binary compatibility in mscomctl.ocx, which is very strange since VB6 "isn't being developed any longer." It is possible to have multiple versions of a DLL or OCX installed that have the same TypeLibID but different Interface version numbers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |