ActiveX oddity - Please Help

[mcmgVB]

Hi all,

I'm not sure this is the right place to post this, but hopefully somebody can point me in the right direction.

I wrote a fairly simple ActiveX control in VB6. It's deployed as an .ocx file along with a HTML/Javascript based IE app. Now here's the oddity, it works fine on most machines but on 1 out of 3 or 4 machines IE crashes.

On 2 machines I have the same version of IE (6.0.2800.1106.xpsp2.030422-1633(Q867801)) and windows (xp sp1), all IE settings identical, all dependency files identical, and yet one works and one doesn't.

When I set IE to prompt ActiveX controls, on the machine that doesn't work I get the ActiveX warning but the control never loads, instead IE crashes.

My control was added to my html page with a simple object tag:
<object classid="clsid:[myclassid]" id="MyActiveXid">

Any thoughts on why it might not be working? Any thoughts on further tests I can do to try to solve this? Any other forums you could suggest that might be able to help me with my object?

Thanks in advance for any help,

Mike

[edit] ps This is all being deployed client-side

[brenaaro]

Does the control load in other browsers, like Firefox?

[Calibra]

Don't know if it's possible in VB, but in C++ you can debug ActiveX.

[mcmgVB]

Thanks for the responses.

I don't think it would load in firefox since I believe firefox does not allow activex controls. But that's ok because it's only designed for a small group of users that all have IE.

In VB you can walk through and debug the control, but everything worked great when I did it that way.

When I checked for dependencies only a few dlls showed up, so I made sure I packaged those. Well it turns out when I use VB's Package and Deployment Wizard (as opposed to manually doing it) a couple of Microsoft .ocx files were also included. Included those files and sure enough it works.

It completely explains the apparent randomness of it working on some machines and not others. Those that had additional software installed that put those same ocx files in the system it worked fine whereas machines that did not have previous software install the ocx files it failed.

M