Problem viewing activeX control on page

[timberbt]

I used the package and Deployment wizard to create a .cab file, I also added in the .lbk file for the licensing stuff (just in case!). I use the web page that the PDWizard creates and then the problems start.

It works GREAT on some machines and on others it just does not load. I can't find any rhyme or reason to it. I have two machines, both win2k, both with IE 5.5, and I have the site listed as a trusted site. It works on one, it doesn't work on the other. All the dependencies of the .ocx are supposed to be included in the .cab file if I read it correctly, and even if they weren't I went ahead and installed another machine it wasn't working on with the newest MDAC, and VB Run times to EXACTLY match the versions on my machine (XP) since I knew it worked on my machine...No luck. Still didn't work.

If I search in the registry for the name of my control it does not show up as a class so it isn't even getting registered.

The codebase location must be correct since one of the machines gets it. Both accounts I viewed it under were local administrators on their machines. I'm really stumped. Is there any way to get any error codes back on why I get the red X where my control should be? Any help would be greatly appreciated as this is my first ActiveX control (I'm actually porting over an application that was previously not web accessible).



Thanks in advance...

[Jacob438]

did you ever figure out what your problem was? I am having similar problems, with IE5.0 and IE 6.0, I don't think it is browser specific, because I can get it to work on IE 5.0 and IE 6.0 on some machines, but not others.

But basically my activeX control isn't being downloaded or run. When I go to the URL, it quickly goes to a blank screen with the little red x. Whereas on a machine that works, it takes a little time to download the control before it works. I have the setting for IE set to Medium Low and my control is signed and marked safe for scripting and initialization.

Any ideas?

Oh yeah, all these machines are Win2k

Jacob438