The OCX files

Hi guys, have searched google and found a few programs to do this but I figured its best I ask here...

For example, one of my programs uses:

Microsoft Internet Controls
System32\asctrls.ocx

Microsoft Rich Textbox Control 6.0
System32\RICHTX32.OCX

Microsoft Windows Common Controls 6.0
System32\MsComCtl.ocx

Microsoft Winsock Control 6.0
System32\MSWINSCK.OCX


Now if the user is missing these files its going to be a pain for them to find and install each one. I am aware there are programs to install missing files but is there one which will install the above? or can be changed to install certain ones etc? so IF the user is missing files all he/she has to do is open one .exe file which will install what is needed?


Thanks :wave:

Those aren't the only files that are used by your program, others will be needed too.

You should create an installation package for your program, using Package & Deployment Wizard (which comes with VB) or similar. This will find all required files, and make sure they are installed on the users computer.

I have moved this thread to the Application Deployment forum, which is for issues like this.

If you include all of the above in your project and then build distribution - all files will be copied and registered when program is installed.
Also, before compiling you will need to:

- open project properties
- select Make tab
- uncheck "Remove information aboun unused ActiveX Controls"

Quote:

---

Originally Posted by si_the_geek

Those aren't the only files that are used by your program, others will be needed too.

You should create an installation package for your program, using Package & Deployment Wizard (which comes with VB) or similar. This will find all required files, and make sure they are installed on the users computer.

I have moved this thread to the Application Deployment forum, which is for issues like this.

---

Do you have any more information on this? I can't find it, also I have never made an actual insallation program

I would recommend compiling your program first, using the "Make" option on the File menu in VB.

P & DW should be on your Start menu, close to VB itself. It is a fairly simple interface (with a built in help system), so you should be able to work it out - but feel free to ask if you get stuck.

I used the program and have it working. My only concern is the setup file has to have SETUP.LST and PROGRAM.CAB in the same path as setup.exe, so basicly 3 files. I was sort of hoping for just one "setup.exe" ?

In that case I think you will need to use a different packaging tool, as P&DW is limited.

There are others listed in the Deployment FAQ at the top of this forum. A common favourite is Inno Setup, and there is a link in that thread to explain how to set it up for VB projects.

Thankyou for all the information. I checked out Inno and it seems great, just a quick question is I can get away with asking it here.. on inno could I have it install my exe and also install whichever ocx's I used in the exe into system32? then just have the user download the vb6 runtimes self installer if they face any problems? would that cover everything? thanks

You can ask any installation questions for your programs in this forum, even if they aren't VB related. ;)

It is risky to install the ocx files into the system32 directory, as you may overwrite ones with the same name which are needed by other programs (and will therefore 'break' those programs). I would recommend putting them into the application folder.

Asking the user to download extra files "if it doesn't work" is risky, as the runtimes include patches which affect several things, and may not be obvious. If the user has an older version installed already then the program will probably seem to work, but will be likely to get errors that dont seem related (such as bugs in certain controls). You should include these with your package - there are ways of only installing them if required (I'm not sure how, but I think you just need a modification to the script file).

Why would you want the user to download anything? If you include the VB runtime files in your setup and the one on the system are the same ones they will not get updated anyway. If they are older then they will. I don't understand your question.

The ocx's by default get copied to the system32 folder and registered. If they are older than the ones on the system they will not get copied or installed. Again I don't understand your question.