>>You could certainly write a VB DLL that would register another object. We do this all the time with VB DLL's. Then, you could just call that page to do what you need. Then you have all those security issues too. :)
>
>Is that utility public? I would like to benefit of it to register the control.

We just hand-coded it.

One thing that we have used is a DLL that is part of the Setup wizard. It's called VB5STKIT.DLL. It has a function to register DLLs in it. You can get the calls to reference it from the Setup source code the MS provides with VB.

Another way, is to just declare a function with the desired DLL. Each ActiveX DLL (by definition) has 2 entry points. One, is DLLRegisterServer and the other is, remarkably, DLLUnregisterServer.

So, if you can access the windows API from an ASP page, and I'm not sure you can, then you could just make the calls. Otherwise, you can create an ActiveX DLL that would do this for you, and you would just instantiate the object from that DLL, and call a method passing a dll filename.

Let me know if I'm not making sense, and I'll walk you through it more slowly.