Your compiled program does not contain all the code that it uses. Most of the windows code is contained in DLLs and ocx files. When you deploy your program you might also have to deploy some (or all) the DLLs and ocs files.
Before doing anything, download a copy of dependency walker (link) to find out what DLLs and ocx your program uses. Then you will have to check the target computer to find out which ones it is missing. Be careful not to overwrite old DLLs on your computer with newer versions on the target computer. You need to do version check before installing your DLLs and OCX files. If you use an auto installer such as InstallShield it will most likely do all that for you.
As an alternative, check your compiler settings and see if it will statically link the DLLs and OCXs so that they are not needed on the target computer. But that will probably double the size of your program. I don't know if vb 6 has such an option or not.
Ancient Dragon
Achieved Level 70
32,274 posts since Aug 2005
Reputation Points: 5,852
Solved Threads: 2,590
Skill Endorsements: 70
Question Answered as of 4 Months Ago by
Ancient Dragon