Problem while making an exe
Hi Gents,
I have created a VB project, when i run it locally, it runs all fine.
I make an exe using File --> Make xxxxxxx.exe option to make an exe file.
This exe file launches the application & works well when i launch it from my local machine.
but, when i copy this exe file to another machine & try to execute it, i get an error - "component 'FTPX.OCX' or one of its dependencies not correctly registered. a file is missing or invalid"
Generally, when we make an exe, we assume that anything that is related to this package will be taken care while creating the exe. But something is missing here, i do not know if there is an option to specify like - include everything in the exe.
Please help me out.
Thanks a lot in advance.
Re: Problem while making an exe
Many times the application you are creating will be referencing other OCX or DLL files that do not exist on the other PC.
To ensure everything the application needs, you should create a Setup.exe file. Using VB's Package & Deployment Wizard will do this for you. Then the entire app can be installed on another pc and later uninstalled if desired.
Re: Problem while making an exe
Thanks for the reply LaVolpe.
I am in the mid of package & deployment wizard, i get a warning window with message: " Below is the list of files for which the dependency information could not be found. To proceed without the dependency information for the file(s) ........blah blah "
There is a list of DLL & OCX(including the FTPX.OCX file that i mentioned in my original post here) files with check boxes.
What do i do now ? Should i check them ? or leave them unchecked ?
Re: Problem while making an exe
If you do not check them, they will not be included with your setup.exe
I think the only recommendation for not checking any would be that if you knew they would already exist on the other PCs.
Re: Problem while making an exe
This PDW (Package & Deployment Wizard) that comes with vb6 is pretty good but I prefer using Inno to make a package. It is a free download you just have to google it. I run the vb6 PDW first and it will create a folder called support, this folder has all the stuff your program will need to run on another computer. I then include it while running Inno's wizard.
The reason I prefer Inno over the one for vb6 is that Inno can create a desktop icon for your program during installation.