I have several utilities that only need the runtime DLL.  XP comes
with the runtime DLLs included, does Windows 2000 come with them too?

jim
using VB5

AFAIK, it does.

I am sure there is always the exception, and you may need to install an
updated version.

Caution, if you need to install VB runtimes, it is best to retrieve the MS
packages for that purpose from the MSDN download site. Never, install
specific components as part of a software package - there is just too many
opportunities for confusion and failure.

hth
-ralph

Yes.  And AFAICT, NT4 >SP2
Show quoteHide quote

You should be safe. According to the DLL Help Database, msvbvm50.dll version
5.2.82.44 is installed with Win2k

Go here, select 'By File Only' and enter the name of any DLL you're worried
about.
http://support.microsoft.com/dllhelp/

Yes, but is it safe to install your app (that was compiled with vb6 sp6)
onto a Win2k or WinXP PC that has pre SP6 runtimes.

Regards

Ken Halter wrote:

Show quoteHide quote

If you create a setup package that includes the newer runtimes, it should be
Ok. I don't use SP6 (Windows Update slides things by though) so I can't say
for sure. Our packages include everything because we still target NT4 and
can't count on anything at all <g> Besides, once we graduated to burning CDs
for our install packages, we make the most of the space we have available
and just include everything it takes to run the app on a PC with no runtimes
at all (those PCs are rare).

Go to the DLL Help database and check. You may be surprised that some
WIndows Updates are installing things you don't know about.... including
newer runtimes and components.

Yes, but with a caveat.  All of the various versions of the msvbvm60.dll
files are binary compatible with one another.  Therefore, if you have the
SP6 version (6.0.97.82) on your dev PC and a target PC has an older version
(say the version that originally shipped with VB6; 6.0.81.76) AND you do NOT
update the target PC, your app will still run.  However, your app may suffer
from any bug that exists in the older runtime file that was fixed in the SP6
version of it. Since you use the SP6 version on your dev PC, you wouldn't
encounter the bug during development and testing on your dev PC.

This is not limited to just msvbvm60.dll.  This would apply to most any
component file such as an OCX or other DLL (as long as all are binary
compatible).

As Ken noted, Windows Update automatically updates many components used by
VB (the runtime as well as OCXs included with VB).

Thanks much for the incredibly quick replies.

jim

Customer asks for database password & link in
Capture the Computer Desktop
decompile exe
Common controls
Tidy Code software
HTML from URL (and back)
Drag and Drop
Track Files Copying Out Of PC
event propagation
XMLdoc for VB