I've created an application in VB4.  The last time I distributed it, I
only distributed the application (.EXE file) and a copy of
VBRUN300.DLL.  The program ran fine on WIN 3.1, WIN 95, WIN NT 3.5x, and
WIN NT 4.0.  After making a few minor changes and recompiling, the
client computers are now asking for VB40016.DLL or VB40032.DLL.  I
recompiled in the same 16-bit environment as before.  What caused this
new DLL dependancy to appear?  How can I fix the application so it works
with VBRUN300.DLL again?

Sorry, there's no way around that.

        - Chris Kyarsgaard
--
+----------------------------------------------------------------+
| Geronimo Development Corporation    Phone: (800)457-6045       |
| 606 25th Ave. S., Suite 206          Fax: (320)259-9808        |
| St. Cloud, MN  56301            WWW: http://www.casefinder.com |
+----------------------------------------------------------------+

If it was originally created w/VB4, the fact that it ran indicates
that the user had VB40016.dll already on their system.

When creating an app in VB4 you MUST distribute VB400??.dll, unless
you know the end machine has the files alredy.

If you use the setup wiz. it will create distribution disks for you.

If you have a copy of the old exe file, inspect it with a hex editor, to
find a reference to either vbrun300 or vb40016.

VB puts the required runtime system into the exe files, as required for all
Windows executables.

DoDi