Installshield For Vb6 Tutorial Visual Basic 6

You need to be a little clearer about some of this. 'Front end/back end' is really terminology and a thought pattern from the MS Access world. It doesn't really apply to VB6 development in any meaningful way unless you're doing something really odd like automating instances of MS Access.

Jan 29, 2018 - Create Visual Basic Installer in easy step using Package and Deployment wizard. Help me hi i know how to make installer in vb6 by using the. Windows Installer Merge Modules provide customers with packaged forms of the redistributable files in Service Pack 6 for Visual Basic 6.0 and Visual 6.0 C++ (SP6) for use with Windows Installer.

That's about the only place where any 'MS Access runtime' comes in as well. If you're actually using Access Reporting you might be doing this though - which seems odd but anything is possible. Much more likely what you are trying to say is that you have a VB6 program that is using a Jet MDB as an embedded database, and using Crystal Reports 8.5 for reporting.

There should be no issue about any 'runtime' for Jet on Windows XP, since Jet 4.0 is shipped as part of the OS even as far back as XP RTM (gold). It is also extremely unlikely that XP will have an MDAC release any older than 2.7 (see ). So this leaves you looking for a way to package your VB6 program, any immediate dependencies such as possibly the VB6 runtime components, and the Crystal Reports 8.5 runtime components. You may also have INI files, etc. To bundle in there. A long, long time ago (1998?) the PDWizard was replaced for most purposes by Visual Studio 6.0 Installer 1.0, and shortly after was released (1999?) which made up for a number of ills. This is a pretty basic tool for authoring Windows Installer packages, but it should meet your needs.

Along with this you'll want the recent merge modules for your dependencies:. Then of course you need a merge module for Crystal Reports 8.5, and for this we have to turn to the community because BO didn't start releasing them until CR9. One place to look for this is. Your real problem is that CR8.5 is ancient. If this doesn't work out for you, you can always hope that CR8.5 Dev installed on your machine with a 'good enough' set of.DEP files (which tell setup authoring tools what subdependencies each dependency has, among other things). This may still let you use VSI 1.1 to succesfully package your application with CR8.5. You might also look at for-pay packaging tools as already suggested.

If desperate enough you might look at some legacy installer technologies too, just in case their communities have addressed your issues. If I misunderstood and you really do use your VB6 program to automate an instance of the 'MS Access 2003 Runtime' you'll probably have to build some hybrid package. Driver hisense andromax u2 dual gsm.

But normal VB programs do not use Access or Access Runtimes to open and work with Jet databases.

I am trying SB Developer to create an installer for my Visual Basic 6 product. I've looked in the Manual and haven't been able to determine the following; I can see how to add the VB6 runtimes but have a question; The VB6 runtimes appear to all get installed in the same direction as my application. That is undesirable.

It looks like I can install them elsewhere; but if I do will there be any steps needed to 'register' them? Will my program be able to 'find' them?

I have experience with Install Shield Express and that product by default seamlessly and invisibly installs the VB runtimes 'somewhere else' (windows/system???) and then registers them. Does SetupBuilder Developer provide something similar, or if not how do I manually do it? Please advise - thanks!

Hi Friedrich, I built one installer and did a trial 'installation' with it and it successfuly installed the program and when I looked in the installation directory all I saw was my executable file. Then I went back to SB and did a 'Dynamic Scan' of my program and built a new installer and ran it. This time when I looked in the installation directory I still saw my executable, plus a lot of files that look like part of VB6; mscomct2.ocx commctl32.ocx tabctl32.ocx and others.