vb4 executable won't run in 3.1???
Quote:
> >Subject: vb4 executable won't run in 3.1???
> >Date: 12 Dec 1995 19:22:23 GMT
> >I'm developing a program with VB4 installed on WfW311. When I run the
> >program on that machine, it works fine. When I copy it to another
> >generic WfW machine, it says "This program requires a later version of
> >Windows." Would anyone know how to get this second machine to run my
> >program?
> For some reason MS didn't change the name of the vb4 Common Dialog dll. Check
> the version and upgrade COMMDLG.DLL.
Unfortunately youv'e uncovered another VB4 "undocumented feature". The problem, in
addition to not changing the name of several dll's and vbx's have now converted your
vbx's to ocx's. AND simply copying these ocx's to the older system won't help you either
unless you understand how to register them in the registry. The easiest way to fix
this is to use the new setup wizzard and then install the program on the other machine.
This will automatically update the registry and any other dlls/ocxs you need.
Here's where it gets fun.... If you are using any VBX's along with your OCX's in the same
project setup wizard has a cute "undocumented feature" and craps out! If this is the
case then what I've done is make a bogus project (a blank form with a couple of the new
ocx's on it) run setup wiz on it and while in setup wizard remove the bogus form and
add all of my real project files!
Isn't upgrading fun! You'd think that MS would spend a little bit of money on de-bugging.
Have you tried minimizing VB4 in Win95? On at least half of our machines VB4 dissappears
completely (yet remains in memory). Perhaps VB5 will be better.
-Mike
