missing *.ocx file in complied *.exe

[daveleo]

hello

re: VB6 ....

i am mis-understanding something about compiling a *.exe file and including all the *.ocx files necessary to run it.

i succesully compiled and ran several *.exe programs and ran them on my (WinXP) computer. i did this using the compiling package that comes with VB6. the programs also ran on my Win2000 laptop.
then i posted the executables on a website and downloaded them onto a *different* computer (WinXP) computer. when i tried to run them, i get error messages about missing *.ocx and *.dll files. (for example, the microsoft tabbed index control .ocx file was missing).

obviously i am missing a step or two or three in the packaging process..... or am i missing steps in the coding (reference statements???).... can anyone point me in the right direction?

thanks, in advance.

daveleo

 

[chiph]

When you package your application, you need to include all of your app's dependencies as well. If you're doing database stuff, you would include the latest MDAC in your setup script. If you're making calls to .ocx and .dll files, they would need to be in there too.

Exceptions would be files which are distributed as part of the operating system, internet explorer, etc. You don't want to distribute them, as you'd be sending files for a Win2k system to a computer running win98 (for example), and you might end up making the win98 machine unbootable.

Your setup tool should have the redistributable packages available for you to select them for distribution (unless you're using the lame P&DW that comes with VB).

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first

 

[daveleo]

chiph

that puts me on the right track.... but i have a follow-up question..... i am only implicitly "calling" ocx and dll files by using various controls....so your point is that i need to learn what files are implicilty called by each VB control and then be sure to package that with the program.

and...uh....yes i am using the lame P&DW that came with VB (i am not a professional programmer).... if you were to recommend decent but SIMPLE software to do this what would you recommend (i wouldn't need all the pro bells and whistles, but i want my stuff to run without getting lots of phone calls from users).

thanks for your reply.

daveleo

 

[chiph]

I've had good experiences with Wise (

http://www.wise.com).

Others have reported good experiences with InstallShield Express (

http://www.installshield.com)

and Inno Setup is free (

http://www.jrsoftware.org)

but I haven't used it.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first

 

[Miners47]

The standard PD&W that comes with VB6 should show you all of the "dependent" files which will allow you to check or uncheck these files as needed before the install package is actually created. By default, the necessary files (OCX, DLL files) are checked to be included in the package.

Since you are installing on a WinXp machine, do the users that are installing this package have sufficient security privledges on the local machine to register DLL & OCX files? You might check to see how these users are setup on the local machine, as I have had similar problems in the problems in the past with Win2000 & WinXp installs.

 

[strongm]

>i posted the executables
>i am using the lame P&DW

These two statements seem to contradict each other.

 

[daveleo]

strongm

yes they do.
not only did i screw up packaging the files but i only ftp'd the executable to the website and downloaded that for the test case. (what was i thinking?)
altogether, i need to educate myself of this process.....running executables on my machime is one thing, setting up to download and run by other users (my students) is not nearly as simple as i thought it was. (which is probably why i don't do this for a living!!)

thanks to all for the replies.

daveleo