,,,,for a guru,,,,

I want to distribute a couple of VB exes.
It seems that a VB exe needs runtime DLLs to be present
to ensure that it works on all platforms.
If I copy MSVBVM50.DLL into ...Windows\System, will
this guarantee that my exe will work in all PCs

It should. But there can be other factors that affect it such as making sure you copy all of the OCX controls you used as well as the DLL's and Type Libraries that you used. Memory, registry space etc. can also be factors so make sure you do system checks before you install your Application.

Thanks for your help
I was hoping that you would pick up on this one
There are no OCX etc so I should be OK

These may possibly be needed:
asycfilt.dll
oleaut32.dll
alopro32.dll
msvcrt40.dll
comcat.dll

They seem to be collected nearly every time by the VB setup wizard.

You may also need ADO/DAO dlls if your app does any database stuff.

Use the Dependency Walker that comes with Visual Studio to see what you need... (I'm not sure how comprehensive this is tho).

Best bet... make a setup program with the Application Setup Wizard thingy then see what files that packages with you program and where it puts them. (Then sack off it's stupid setup program.) :D

If there's a lot of files needed and you wanna make your own installer then keep it simple (no extra activex controls etc) and just include the standard vb runtime (msvbvm50.dll/msvbvm60.dll) in the same folder as the setup program. I've done this on CDs and it works fine. Another thing...for setup programs try to stick to VB5...VB6 programs need OLE 2 which is not standard on older Windows installations.

I thought OLE2 was standard on Win95 and above. Is it different, then?

Don't think W95 (v1) has it. Not sure about NT.
I've made a program (with standard setup package) in VB6 and when you install it on an older Windows installation the setup program has to reboot the machine to update OLE 2.

Must've been an update of the original version of OLE2, because Microsoft said that OLE2 was one of the new features in Win95, way back in 1994/5.

I thought that it it was done in Internet Explorer 4, Win98 etc...

Dunno... know a few machines at work needed updating. Some of them might be running NT4 now I come to think of it... hmmm.

Jackbee: If you are using the P&D or VB Setup Wizard, I don't really think there is anything for you to worry about. The wizard will add all of the necessary files for you.

Sorry, but we've been through that stage, Mega. Now we're trying to confuse people. (Albeit not very well.) :D

Thanks for your contribs guys
The reason for the original thread was :-
An Access mdb packed with 97 ODK included MSVBVM50.DLL
which by default went to $winsys (windows\system\).
It also included a couple of small VB exe's.
A user claims the mdb was fine but couldn't run th VB?????
I don't understand this as the MSVBVM.. must have been
in the correct place and as far as I know it doesn't need
registering
Can anyone thing why this happened???