从VB 3.0迁移到VB 6.0 [英] Migration from VB 3.0 to VB 6.0
问题描述
我确实有一个VB3 16位应用程序，它运行在一台非常老的Pentium I机器上，自1995年以来一直运行Windows 3.11
。应用程序运行正常但PC需要紧急升级为
!!
VB3使用VBX组件代替OCX或类或任何.NET新版
东西。我怎么能测试我是先在VB6上运行（1）还是在（2）在32位操作系统（如2000 / XP）上运行它？
非常感谢任何提示或评论。
" Old_VB3_User_MX" < 01 ************* @ discussions.microsoft.com> schrieb
我有一个VB3 16位应用程序，自1995年以来在一台非常旧的Pentium I
机器上运行Windows 3.11。应用程序运行正常，但PC
需要紧急升级!!
VB3使用VBX组件而不是OCX或类或任何.NET新东西。我怎么能测试我是否会先在VB6上运行（1）
和（2）在32位操作系统（如2000 / XP）上运行？
非常感谢任何提示或评论。
VB.Net是VB的最新版本（VB6是1998年）。这就是这里讨论的
。旧版本在许多
microsoft.public.vb。*组中的一个处理。
您必须购买与VBX版本兼容的OCX - 如果
可用。转到制造商找到这个 - 如果仍然可能。
安装OCX版本后，应该在[VBX
Conversions32]部分添加一个条目vb.ini文件，您应该能够加载
项目 - 当然，使用项目的副本 - 在VB6中并将其转换为
。我不记得之后还有什么事要做，因为我几年前最后一次这样做了b $ b，但是在上面提到的各组档案中，b / b
，你可能会发现很多关于它的消息。
在XP上运行VB6应用程序没有问题（除非你使用特殊的
Win 3.11功能不可用在更新的版本中 - 但我不能
记住当前的任何内容。）
Armin
< blockquote>Armin Zingler < az ******* @ freenet.de>'狂野的想法是在星期二，2005年8月23日01:05:15发布的
带有
关注水果：
" Old_VB3_User_MX" < 01 ************* @ discussions.microsoft.com> schrieb
我有一个VB3 16位应用程序，自1995年以来在一台非常旧的Pentium I
机器上运行Windows 3.11。应用程序运行正常，但PC
需要紧急升级!!
VB3使用VBX组件而不是OCX或类或任何.NET新东西。我怎么能测试我是否会先在VB6上运行（1）
和（2）在32位操作系统（如2000 / XP）上运行？
非常感谢任何提示或评论。
VB.Net是VB的最新版本（VB6是1998年）。
Bah！ VB.Net是一种*新*语言与
VB1-6没什么关系。
J
这是这里讨论了什么？旧版本在许多
microsoft.public.vb。*组中的一个处理。
您将不得不购买与VBX版本兼容的OCX - 如果
可用。转到制造商找到它 - 如果仍然可能。
安装OCX版本后，应该在vb.ini文件的[VBX
Conversions32]部分添加一个条目，你应该是能够加载
项目 - 当然，使用项目的副本 - 在VB6中并将其转换。我不记得之后还有什么事要做，因为我几年前最后一次这样做了，但是在上面提到的小组的档案中，你可能会发现很多关于它的消息。
在XP上运行VB6应用程序没有问题（除非你使用特殊的
Win 3.11功能在新版本中不再可用 - 但我不能记得任何目前的。
Armin
Jan Hyde（VB MVP）
-
冒着重复自己的风险，我再一次告诉那群克隆人我会给他们一些我的DNA样本。
（来自Ruminations的Harrison Cockerill）
[废除电视许可证 - http://www.tvlicensing.biz/]
" Jan Hyde" <圣*********** @ REMOVE.ME.uboot.com> schriebVB.Net是VB的最新版本（VB6是1998年）。
Bah！ VB.Net是一种*新*语言，与VB1-6没什么关系。
嗯...是的。
Armin
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.
"Old_VB3_User_MX" <Ol*************@discussions.microsoft.com> schrieb
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
"Armin Zingler" <az*******@freenet.de>''s wild thoughts were
released on Tue, 23 Aug 2005 01:05:15 +0200 bearing the
following fruit:
"Old_VB3_User_MX" <Ol*************@discussions.microsoft.com> schrieb
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).
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/]
"Jan Hyde" <St***********@REMOVE.ME.uboot.com> schriebVB.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.
Ummm.... yes.
Armin
这篇关于从VB 3.0迁移到VB 6.0的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
