For very simple applications you can get with just the VB6 VM DLL but anything practical needs a bunch of OCX controls - even if you stick with the stock stuff you get with Visual Studio 6. AFAIK those OCX controls come with Windows for some years now so you can give someone a VB6 .exe and it'll work, but if you need anything outside of that you need to register them (unless i am wrong and VB6 can freeform OCX files directly but i'm almost certain it can only use stuff registered with the system).
Delphi VCL can use COM objects but on Delphi this is an exception rather than the norm, components on Delphi are (or can be) statically linked with the application. For VB6 the norm is using OCX controls... actually, i do not think it is possible to do anything else (outside of manually calling DLL functions of course, but even that is relying on a separate DLL).
Delphi VCL can use COM objects but on Delphi this is an exception rather than the norm, components on Delphi are (or can be) statically linked with the application. For VB6 the norm is using OCX controls... actually, i do not think it is possible to do anything else (outside of manually calling DLL functions of course, but even that is relying on a separate DLL).