>>The control has two different types of licenses. One for runtime, one for design time. It's best to do an install that'll take care of the proper registration issue for you.
>
>George,
>AFAIK, there is only one license and that is the development license. The ActiveX control is freely distributable and creating an install program using Setup Wizard (or anything else) will only copy and register the control itself. The license information is not freely distributable.
>
>Most ActiveX controls act this way (at least the ones I have encountered). They have a "secret" registry license key or a LIC file associated with them. When the object is created (dynamically using AddObject/NewObject/CreateObject or dropped on a form) the control checks to see if the user has the appropriate license information. The dynamicness is the key that vendors use to determine if the control is being distributed as part of an application or in a development environment. The former they don't usually care about; the latter they do.
>
>If the control is embedded on a form and the control has been registerd using RegSvr32 (or the internal function), then everything is usually okay. If not, you get the dreaded license error.

Larry,

A similar issue with this control was covered sometime back in the MSDN News. There are two licenses, however: one for design time, one for run-time. If you're going to add the control either through a prg or AddObject, you need the design time license. Therefore, for distribution, you need to physically add the control rather than say, trying to sub-class (which to me would be preferable in order to avoid versioning issues) it. There are a couple of MS KB articles on this. Most appropriate to me to this issue would be Q139154 and Q192693.

You are correct, however, the RegSvr32 will work if the control has a physical presence. Otherwise, it won't.