This seems to be the only place to turn for COM Interop problems (outside of directly pestering a few select people). So thanks in advance for any help. I have posted this on the ActiveX section of the windowsforms.com forums as well. I will share anything I learn here in that spot. ------------------
I basically solved the bizarre problem of dealing with license keys for my own ActiveX controls when using them in my winforms application. But I am having a strange problem. I have about 20 controls in an ocx file that I access dynamically from my winforms app. This via an AxIMP generated dll. When I use the controls on my dev machine, all is well. (but of course!! <g>) When I deploy them to another box (I have tried two others so far with similar results), all but one of the controls work. On that one, a message box pops up to say "you don't have a license to use this activex control." I have triple checked the license key that I have tucked away in an embedded resource file. Plus there is a VB app that uses the same controls from literally the same ocx file and it can access that particular activex control on these machines. I know COM interop is a wily beast, but has anybody seen behavior like this and have any ideas what I should be looking at to fix it? Thanks much. Julie Julia Lerman VTdotNet User Group Leader www.vtdotnet.org <http://www.vtdotnet.org/> INETA User Group Relations Committee Co-Chair <http://www.ineta.org/> www.INETA.org Microsoft MVP
