Deployment Question 2

[Sam13]

I've designed an application using VB 6.0 which utilizes ADO controls and an access database. The program and its executable file work great on my PC off of a network drive. The OS is Windows NT. The problem is that the executable file does not work off of the network drive from other PC's. Is there something more that I have to do in order to get this to work. I didn't create a deployement package. I just created and .exe file. Thanks for any advice.

Sam

 

[JohnYingling]

The objects that your project references must be registered on each machine whether or not they are physically present on another machine, starting with MSVBVM60, the VB6 runtime. The network drive that you are running from is still a drive on each client. You must install on each machine even though the install will point to network drives. How else does your app know from where "ADODB" can be loaded.

http://WWW.VBCompare.Com

 

[IonelBurtan]

You have three solutions:
(The third method on you should use only if you have done something similar before)

1. Look for exe file name mdac_typ.exe(ADO kit) in you SP5 for Visual Studio kit. Run it on the target computers that you want to use your program.

2.You make a deployment kit - with Package and Deployment Wizard which you can find in Visual Studio 6.0, and than install this kit on the machines you want.

3.You copy the required files and install them on the computers you want to use your program.
- to find out which files are needed you do this:
* you make a kit with Package and Deployment Wizard in a specified directory
* go in the directory where you have made the kit - you should see a subdirectory called "Support" which contains all the files you need to install or copy on the target machine
* you copy all DLL and OCX files from that directory to the system directory of the target machine
- to install al COM components files are needed you do:
* then you register all with regsvr32.exe from a command prompt or .BAT file.

Hope of being of some help, s-)
Blessed is he who in the name of justice and good will, shepards the week through the valley of darknees...

 

[bosully]

Running the Package and Deployement wizard is probably the handiest solution.

Just be careful when installing on other machines with an Access installation. I've done this and found instances where users had newer versions of Access than I had on the development machine causing a few hiccups.

Brendan