Dex, it's puzzling to me why I had to register the TypeLib after I compiled, but I was always under the impression that making ActiveX components placed things in the registry during compile. I'm going to guess that it's just the TypeLib info that didn't get auto-registered when compiled, but the actual ActiveX.dll (or ActiveX.ocx) did get registered when compiled.

I'm not sure there's a way to stop the VB6 IDE (or the VB6.exe, if compiled from a batch file) from auto-registering the component. At least I'm not able to find a switch anywhere to do this. You can probably check the "Project Compatibility" or "Binary Compatibility" switch to keep it from auto-registering with different UUIDs more than once, but I don't think there's a way to completely suppress the auto-registering.

I'm pretty sure this is the registry cluttering that Bonnie is talking about.

TypeLibs used in the way discussed in this thread (just to get UDTs into Variants), there wouldn't be any registry cluttering of client computers, unless you did include the superfluous DLL in your package.

Regards,
Elroy