>Yeah, it wasn't registered - gave an error - and then the licensing thing. Trying to make the install for our network guy as seamless as possible. I created an app that is used to intall/setup/start/stop and monitor the service and would like to have as few hiccups as I can when we start distributing.
>
>You know, I was thinking about this one this morning. Doug's article is definitely something you should read and you will definitely find it helpful. However, I thinkt hat the solution tpo your problem is much simpler really.Why not just include the ocx in your installation program. That way it will be installed and registered and the above is not an issue.

Well, I was thinking along those lines as I do the same thing with the instsrv and srvany files I need to install and run the service. I guess I thought that I was thinking in a "workaround" way instead of in the way of good development. So, put the OCX in a memo field in my included table then bring it out and use it during installation?