Should i have to distrubute .ocxs?

[iataman]

Is there a way to make programs include all the functions, procs , controls etc. and so we wouldn't have to distribute
dll's and ocx'with our programs.

I made a tiny program, 12.4 Kb , and packaced it the VS's "Package and Deployment Wizard" to its 4MB!!

Thanks in advance.

Only distribute the controls that you are using in your App, do not include the rest. Most of that 4MB is the VB Runtime files.

[Andrew Empson]

The only way you can distribute an application and be fairly sure it will work on most machines is by packaging it up with the OCX files and DLLs.
If you use a program like BitArts Fusion, which takes the relevant routines from the DLLs you use and bundles these routines into the final EXE file, you won't have to include the extra files, but you'll find your EXE file has gone from 12.4k to 2 or 3 Mb, and may not work on some systems any more.
It's one of the limitations of VB that Compiled files require BIG runtime DLLs, and if you want to make a program which is actually 12.4K, you'll have to do it in another language.
If you know for certain that people who will be using your program have VB, then you won't need to include the DLLs, and your EXE should be OK, as long as they have all your custom controls too.

[MartinLiss]

I agree that the only weay you can be sure it will work is if you use the Package and Deployment Wizard.

One thing you can check is that you may have some Components checked in the VB IDE that you are not actually using.