Migration from VB 3.0 to VB 6.0

[Guest]

I do have a VB3 16-bit application that runs on a very old Pentium I machine
with Windows 3.11 since 1995. Application runs OK but the PC needs to
urgently be upgraded!!

The VB3 uses VBX components instead of OCX or classes or any of the .NET new
stuff. How could I test whether I will run (1) first on VB6 and (2) on a
32-bit operating system such as 2000/XP?

Thanks a lot for any tip or comment.

 

[Armin Zingler]

I do have a VB3 16-bit application that runs on a very old Pentium I
machine with Windows 3.11 since 1995. Application runs OK but the PC
needs to urgently be upgraded!!

The VB3 uses VBX components instead of OCX or classes or any of the
.NET new stuff. How could I test whether I will run (1) first on VB6
and (2) on a 32-bit operating system such as 2000/XP?

Thanks a lot for any tip or comment.

VB.Net is the most recent version of VB (VB6 is from 1998). This is what's
discussed here. Older versions are handled at one of the many
microsoft.public.vb.* groups.


You will have to buy the OCXes that are compatible to the VBX version - if
available. Turn to the manufacturer to find this out - if still possible.
After installation of the OCX version, which should add an entry to the [VBX
Conversions32] section of the vb.ini file, you should be able to load the
project - of course, use a copy of the project - in VB6 and have it
converted. I don't remember what else has to be done afterwards because I
did this some years ago the last time, but in the archives of the groups
mentioned above, you will probably find many messages about it.

There's no problem running VB6 applications on XP (unless you use special
Win 3.11 features not available anymore in newer versions - but I can't
remember any currently).


Armin

 

[Jan Hyde]

"Armin Zingler" <[email protected]>'s wild thoughts were
released on Tue, 23 Aug 2005 01:05:15 +0200 bearing the
following fruit:

VB.Net is the most recent version of VB (VB6 is from 1998).

Bah! VB.Net is a *new* language that has little to do with
VB1-6.

J

This is what's
discussed here. Older versions are handled at one of the many
microsoft.public.vb.* groups.


You will have to buy the OCXes that are compatible to the VBX version - if
available. Turn to the manufacturer to find this out - if still possible.
After installation of the OCX version, which should add an entry to the [VBX
Conversions32] section of the vb.ini file, you should be able to load the
project - of course, use a copy of the project - in VB6 and have it
converted. I don't remember what else has to be done afterwards because I
did this some years ago the last time, but in the archives of the groups
mentioned above, you will probably find many messages about it.

There's no problem running VB6 applications on XP (unless you use special
Win 3.11 features not available anymore in newer versions - but I can't
remember any currently).


Armin

Jan Hyde (VB MVP)

--
At the risk of repeating myself, I once again told that group of clone
scientists I would give them a sample of my DNA.

(Harrison Cockerill from Ruminations)

[Abolish the TV Licence - http://www.tvlicensing.biz/]

 

[Guest]

OK, I'll change to the appropiate forum. Thanks for your comments.

I do have a VB3 16-bit application that runs on a very old Pentium I
machine with Windows 3.11 since 1995. Application runs OK but the PC
needs to urgently be upgraded!!

The VB3 uses VBX components instead of OCX or classes or any of the
.NET new stuff. How could I test whether I will run (1) first on VB6
and (2) on a 32-bit operating system such as 2000/XP?

Thanks a lot for any tip or comment.

VB.Net is the most recent version of VB (VB6 is from 1998). This is what's
discussed here. Older versions are handled at one of the many
microsoft.public.vb.* groups.


You will have to buy the OCXes that are compatible to the VBX version - if
available. Turn to the manufacturer to find this out - if still possible.
After installation of the OCX version, which should add an entry to the [VBX
Conversions32] section of the vb.ini file, you should be able to load the
project - of course, use a copy of the project - in VB6 and have it
converted. I don't remember what else has to be done afterwards because I
did this some years ago the last time, but in the archives of the groups
mentioned above, you will probably find many messages about it.

There's no problem running VB6 applications on XP (unless you use special
Win 3.11 features not available anymore in newer versions - but I can't
remember any currently).


Armin