Quote Originally Posted by vb_student
so i need to launch the package and installation wizard which would create an executable which would not need any ocx files whatsoever?

my program accesses a couple of excel files, i think it should have MS excel installed too, the package wizard would not be able to take care of that, correct?

where can i use the .exe generated fro mthe make utility ?
The package and deployement wizard will want your .vbp file. From that, it will determine what dependency files (like OCXs, Dlls, etc) that you will need to run this from a different machine. It already knows what dependency files VB needs. Then it will bundle all of those up into an installation package. This package can be copied to a new machine, and then you can run the SETUP.EXE that will be created that will unbundle all of that stuff, store on the local PC, register all of the files that need to be registered, and you should be good to do.

If you have other files that need to be included, like Excel Spreadsheets, then those will have to be manually added to the installation package. As you walk through it, you will see what I mean.