Problem with ActiveX Control

[sweep123]

I was using a 3rd party ActiveX control with MS Visual Studio .Net under Windows NT.

Now I have upgraded to Windows 2000, but this particular 3rd party ActiveX is causing a problem.
The solution builds OK, but I cant display/edit the dialog as the component cant be instantiated. However the solution builds and runs.
Another program deploys and runs OK when I register the control and fails when I un-register it

Note I have tried re-register the control via:

regsvr32.exe /u air.ocx

and then:

regsvr32.exe air.ocx

I have contacted the 3rd party vendor, but I am out of my 3 month support period. Also another ActiveX from this vendor works OK!

Is there anything I can do within Visual Studio to sort out this problem, as I don't think it is the vendors fault.

Regards,

 

[teriviret]

Why does the control fail to be instantiated? Maybe it's being created but failing somewhere in its own code? Is it some kind of composite control, trying to instantiate some other control, that happens to be missing?

Maybe the component is relying on some undocumented feature of Windows NT, that changed or went away in Windows 2000?

Maybe this component is licensed, and the license file is missing or corrupted?

Have you tried instantiating the control with the ActiveX Control Test Container?

Does the vendor have an online forum where other people may have posted asking about the same problem they've also encountered? Have you searched with Google to see if anyone else out there is using the same control and having the same problems?

 

[sweep123]

The vendor gave a me program to tidy up the registry for the control.

It works fine now, but I could not do this without the vendors help.

I run this program and then register the ActiveX control again - all OK.

Thanks for your input.

Sweep