Using VB 5 with Windows 3.11
Quote:
> I am working with a large network of computers many are Win95 but some
> are still Win 3.11 and won't be upgraded for some time to come.
> Can anyone tell me of problems of upgrading software from VB3 and VB4 to
> VB5 and still running the compiled programs on a Windows 3.11 system?
> Are there advantages to VB5 as far as Windwos 3.11 is conserned over VB4?
> Any help would be greatly appreciated. Thanks!
Well, the first thing to be aware of is that VB5 is 32-bit only: nothing
you compile in VB5 will be able to run on Windows 3.x.
If you need to support both Windows 3.x and Windows 95 (or NT 3.51+), you
might be happiest using VB3 for Windows 3.x and VB5 for your 32-bit work.
VB4 _does_ have 16- and 32-bit versions, and might seem the ideal way to
develop to both operating systems, but VB5 far outshines VB4-32, and VB3 is
faster and more stable than VB4-16. At this point the only thing I would
use VB4 for is converting 16-bit projects to 32-bit.
The main problem you'll encounter moving 16-bit VB projects to 32-bit is
converting VBX controls (VB3 primarily) to OCX controls (VB4-32 and VB5).
If you stick to using the standard Windows controls, or to controls from
established vendors who offer easy OCX upgrades to their VBXs, you won't
have too many problems ... though you may have a few.
Personally, I've had few problems converted 16-bit VB code to 32-bit. A few
others have mentioned having problems, but didn't give details. The core
language hasn't changed that much, and the VB folks have gone to great
lengths (some might say too great) to ensure that code backward
compatibility is maintained. So controls might be a source a problems; code
is unlikely to be.
