DSE
asked on
Package & Deployment Error
Hi,
I'm trying to package my VB program but every time I try to do so I receive an error message:
Error 457 - This key is already associated with an item of this collection.
I can make an executable of this program easily enough but I require that it is packaged with all of its dependant files.
Can anyone help with this error?
Thanks,
David.
I'm trying to package my VB program but every time I try to do so I receive an error message:
Error 457 - This key is already associated with an item of this collection.
I can make an executable of this program easily enough but I require that it is packaged with all of its dependant files.
Can anyone help with this error?
Thanks,
David.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Smg,
I did have a reference to a library in both the components and references.
Can't believe I didn't see that!!!...and why couldn't the error message have said what it was! :-)
Thanks,
David.
I did have a reference to a library in both the components and references.
Can't believe I didn't see that!!!...and why couldn't the error message have said what it was! :-)
Thanks,
David.
Glad I could help.
Hi!
My comment would only be applicable if you did not use any 3rd party ocx files and that you didn't call and dll calls from dll files that fd o not come with the particular version of windows you're sending your proggy over to.
Actually, your program does not need all those dll fils that are packaged together with it.
What you need to do to export your file is this:
Zip up all the ocx files that you've used, + your VB app exe file and the VB runtime file (Msvbvm60.dll). These dll and ocx files can be found in the C:\Windows\System folder or your system folder.
Make a self-extracting exe file that will unzip everything INTO A FOLDER, not seperate folders. Your app, upon extraction should run fine from there :)
Oh yes, include any database, text or help files in the self-extracting exe file if need be.
That's it!
glass cookie : )
My comment would only be applicable if you did not use any 3rd party ocx files and that you didn't call and dll calls from dll files that fd o not come with the particular version of windows you're sending your proggy over to.
Actually, your program does not need all those dll fils that are packaged together with it.
What you need to do to export your file is this:
Zip up all the ocx files that you've used, + your VB app exe file and the VB runtime file (Msvbvm60.dll). These dll and ocx files can be found in the C:\Windows\System folder or your system folder.
Make a self-extracting exe file that will unzip everything INTO A FOLDER, not seperate folders. Your app, upon extraction should run fine from there :)
Oh yes, include any database, text or help files in the self-extracting exe file if need be.
That's it!
glass cookie : )
hmmm,
If every software release did this, we'd have a rediculous number of ocx/dll's on our machines...
Also, things like service packs / upgrades to shared dll's wouldn't be applied to every copy of msvbvm60.dll, just the one in the system folder.
If every software release did this, we'd have a rediculous number of ocx/dll's on our machines...
Also, things like service packs / upgrades to shared dll's wouldn't be applied to every copy of msvbvm60.dll, just the one in the system folder.
Well, he could shift the runtime files to C:\Windows\System folder if you want all VB apps to run using 1 system file in the PC, but someone once told me not to do it.
: )
glass cookie : )
: )
glass cookie : )
ASKER
sorry for the delay...i was sure I accepted your comment already...was surprised to see comments being added still :-)
anyway, thanks for your help,
David.
anyway, thanks for your help,
David.
Pleasure !!
Program Files\Microsoft Visual Studio\VB98\Wizards\PDWiza