| Ken Halter 2006-03-31, 6:55 pm |
| "David Slee" <davidslee_98@yahoo.com> wrote in message
news:u$d3gARVGHA.2492@TK2MSFTNGP11.phx.gbl...
>
> Please be kind as I'm new to VB 6. I've created an VB 6 ActiveX control
> that will be deployed to our corporate Intranet. We have lots of vendor
> applications that rely on VB 6 runtime dlls. How do I distribute the
> control without creating dll incompatibilities? The set of VB 6 runtime
> dlls that are listed in the .inf file created by the PDW for my control
> are older versions than what I'm told is on most of our machines (mostly
> Windows 2000 Professional).
Older is good. The PDW grabs all it can from the redist folder. That folder
contains the "bare mininum" version of the system ocx's/dll's your app
requires. Since any decent installer will skip files on a target PC that are
newer than those found in a setup package, packaging older components is
perfect. The problems start when the files are newer (like trying to install
an OS specific dll, or one that's already in use, from XP onto Win2k)
--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
|