I have a very peculiar and specific case. I develop a VB6 based ActiveX control that I need to work on a different one.
The development machine is a Windows Server 2003, the “production” machine is Windows 7 Prof.
Now, when I package by ActiveX in CAB and run the “demo” HTM-file on the development machine, everything works fine.
But as soon as I copy alle the contents to my production machine, and open the same HTM file (after clicking OK on the ActiveX security warnings and “installing” the CAB), nothing happens (where it should actually open a message box).
How can I debug this? Obvously, the browser does find the CAB, otherwise it wouldn’t even know what to install. But, it doesn’t seem to trigger correctly.
My problem isn’t so much that I didn’t know how to handle errors, but where these errors are? Is there any “Internet Explorer Logfile” that I don’t know of?
After some more research, I found the error. In my enthusiasm for 64bit and the like, I made the 64bit version of IE my default, resulting that I always loaded the demo page with my ActiveX on that browser.
As I know now, this won’t work, because VB6 only compiles to 32bit.
Loading the page in the 32bit version showed that the ActiveX could be loaded and run without problems.
Sorry for the confusion. I tend to forget that 64bit is my default and that, obviously, old languages won’t always work with that.