You can see implicitly related DLL dependencies with Dumpbin / import. Or a static view provided by Dependency Walker. However, VB6 programs are usually heavily dependent on COM components, and they load while the program is running. These components must be registered before the program can download and use them.
To see this, you will need a utility that shows how the program uses the registry. There is nothing in the VS6 toolbar for this, you can use the SysInternals ProcMon utility. Note the program trying to open the keys in the registry key HKLM \ Software \ Classes \ CLSID, where the COM components are registered. You should see that he could not find this key from which you can determine the CLSID.
It still wonβt deliver you, because itβs just an opaque number, it doesnβt tell you the name or location of the DLL. Use Regedit.exe on the computer on which the program is working correctly. Find this key, the value of LocalServer32 will tell you which DLL or OCX implements the COM component.
source share