Executable in VB6.0

I was using VB6.0 and trying to make an executable file that  can work in the computers that does not have VB-6.0 installed, but somehow it kept prompting the message that there's a *.dll file missing even after I copied these *.dll files into the same directory.
Can anyone help me on this? Thanks a lot.
neuralAsked:
Who is Participating?
 
mark2150Connect With a Mentor Commented:
You need to be using the setup wizard to install your software instead of just copying the .EXE and assorted .DLL's. Simply copying the .DLL's is *NOT* sufficient. You also have to register them into the registry. You can do it manually with RegSvr32 or you can do it automatically using the setup package generated by the setup wizard. Once the software has been installed the first time you can update just by copying the .EXE as long as you haven't added an OCX or new .DLL to the project.

Use the tools provided instead of trying to "roll your own" and your life will become *MUCH* simpler.

M

0
 
neuralAuthor Commented:
sorry, mare2150, my writting is too lousy. I think you get confused. Actually, I had written a VB program and runs fine on the machine that has Vb6.0 installed. Now the thing I am trying to do is, make the program I wrote can be executed on other computers which without Vb6.0 installed. But I failed on this, can you help me on this one?
0
 
mark2150Commented:
Like I said. Use the SETUP WIZARD to create an installer. It runs on your development system because all of the .OCX's and .DLL's are already registered. When you use the setup wizard to create the installation package it will place all of the files that your application needs (including .OCX's and .DLL's) into one place along with a customized SETUP.EXE and SETUP.LST. Copy *ALL* of this to the target system and run SETUP.EXE to install. The setup program will install your software just like any other windows applications. It'll put your programs into C:\Program Files\{yourprog}, it'll copy the various .DLL's into C:\WINDOWS and/or C:\WINDOWS\SYSTEM and it'll even add your programs icon to the [Start]/Programs list.

When the SETUP WIZARD runs you'll have several options as to if you want to create a "single directory" or "Multiple Disk" installer. If you choose "single directory" all of the setup and configuration files will be placed into a single directory where you can use PKZIP to generate a "single file" distribution package. Conversely, you can tell it to create multiple directories, one for each diskette. In this mode the wizard will split up your software and installation utilities so that you can copy it to individual floppies. The DISK1 directory will contain the SETUP.EXE program that is used to install your software.

This is the *correct* way to build a distribution setup. Attempting to copy the .EXE and the various .DLL's/OCX's will *NOT* work as you have found out - remember - VB is a *WINDOWS* program, *NOT* DOS!

If you want to see some examples of both methods of distribution (single file and multiple diskette), visit my web page: www.cyberchute.com/rvbus/madmark and you can download several programs I've written and set up using the SETUP WIZARD.

M


M
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
neuralAuthor Commented:
Thank you, mark2150.
0
 
neuralAuthor Commented:
Mark, where can I get this "Setup Wizard" you mentioned? It seemed one of the *.dll file is already in Windows95, but the one needed by VB6.0 is a newer version.
0
 
mark2150Commented:
It's part of the VB kit. Look around on the menu.

M

0
All Courses

From novice to tech pro — start learning today.