package and deployment wizard

[vb_student]

Hello

I am trying to run the package and deployment wizard and followed the instructions with the help file

when i try to add "package and deployment wizard" it comes up with the error.

"error in loading DLL"


originally i had tried to locate it on the "Add-In Manager from the Add-Ins menu" but could not find it that is why i had to resort to adding the PDW

[Hack]

There should be a package and deployement wizard entry under Add-Ins.

Did you load VB from a VB6 Cd, or from a Visual Stuido 6.0 CD?

[vb_student]

found it, thanks

i was looking under the components menu

[Hack]

Have you seen this?

Using The Package And Deployment Wizard (http://visualbasic.about.com/od/usevb6/l/bl0001a.htm)

[vb_student]

thanks for the link hack

i had not seen it, i was just going through the help files on VB

i managed to create the a bunch of files, foo.cab,setup.exe,setup.lst and a folder containing a bunch of ocx's,exes(excel.exe included hmmmm) and a .lst

i tried to use the setup.exe file to install the program on a different machine and it was happily installing the files till it got to msvcrt.dll (the installation complains that the destination file is in-use. please ensure that all other applications are closed"

all other applications are closed, i tried to rerun the setup a few times but come up with the same error

(hey the setup process looks so cool, management should be impressed :) )

[vb_student]

i repackaged the stuff and this time removed msvcrt.dll when i was creating the installation package and it works

but what it also does is create a copy of excel.exe(9 megs) and a copy of the graph (2 megs) and places them in the created destination directory. is that necessary, since excel already exists on the old machine

does this mean that excel as a program is being copied to the destination machine?
i dont want microsoft breathing fire down my neck saying that i was creating illegal copies of excel?

also is there a way to package the excel files i use with the vb project into the .cab or the support folder