For what it is worth, I have never been able to make the "extract COM information" work. I have some ODBC dlls (Sybase) I ship with my app and they have the same problem. Changing to "Self-registration" seems to work fine for me.

>I was messing around with both the mini-InstallShield that comes with VFP9 and an older version of InstallShield Express. I realized that COM DLL's compiled in VFP9, InstallShield was unable to extract the COM information and as a result could not register the DLL's in the registry automatically.
>
>The same behavior is not observed in VFP8 or less. The temporary fix seems to be to right click on the VFP9.DLL in the "Files" window of Installshield. Select properties the select COM / .NET tab and set regestration method to "Self Registering". This will get your DLL registered on your client's workstation but it should be noted that "Self Registered" DLL's sometimes have problems with Window's Installer if the user ever wants to un-install.
>
>I did some digging and found some chatter about a bug that prevents the PROGID from being recorded in the DLL.
>
>Anybody else run into this?