How To Port VB 3.0 projects w/ .Vbx to VB 4.0 16-bit & 32- bit

MORE INFORMATION

For example, if an existing Visual Basic 3.0 project contains Threed.vbx, the corresponding entries must be present in Vb.ini for both the 16-bit and 32-bit versions of Visual Basic 4.0. Both versions of the threed .ocx file should be present in the specified directories:

16-bit

[VBX Conversions16]
threed.vbx=
{0BA686C6-F7D3-101A-993E-0000C0EF6F5E}#1.0#0;C:\WINNT35\SYSTEM\threed16.ocx
				

32-bit

[VBX Conversions32]
threed.vbx=
{0BA686C6-F7D3-101A-993E-
0000C0EF6F5E}#1.0#0;C:\WINNT35\System32\threed32.ocx
				

When you try to open an existing Visual Basic 3.0 project with .vbx files in Visual Basic 4.0 (16-bit or 32-bit), a dialog box with a list of all custom controls to convert is displayed and will prompt you to make the conversion. If you choose to make the conversion, the corresponding .ocx files will be automatically included in the new Visual Basic 4.0 (16-bit or 32-bit) project. If you choose not to convert, Visual Basic 4.0 16-bit will retain the original .vbx files in the new Visual Basic 4.0 project, but Visual Basic 4.0 32-bit will simply not include the original .vbx files.

All .vbx files that are to be converted must exist on the computer where the conversion is taking place. If one or more .vbx files are missing, Visual Basic 4.0 will give the following error message for each missing .vbx file:

There is no way to avoid this message other than by ensuring that each .vbx file is present on the system that is performing the conversion.