INFO: Visual Basic 5.0 and 6.0 Compatibility Issues

ID: Q217017


The information in this article applies to:
  • Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, versions 5.0, 6.0


SUMMARY

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

This article summarizes the compatibility issues between Visual Basic version 5.0 and 6.0.


MORE INFORMATION

Following are the known compatibility issues between Visual Basic 5.0 and 6.0:

  • Running the Visual Basic 5.0 Setup Wizard on a system with both Visual Basic 5.0 and Visual Basic 6.0 installed.

    While you can develop a Visual Basic 5.0 application in a system with both Visual Basic 5.0 and 6.0 installed, you should only create a deployment package for your Visual Basic 5.0 application on a clean system with only Visual Basic 5.0 installed.

    When Visual Basic 6.0 is installed on the same system as Visual Basic 5.0, all the controls installed by Visual Basic 5.0 are updated. The updated controls may cause a problem when you run the Visual Basic 5.0 Setup Wizard to create a deployment package for your Visual Basic 5.0 application due to different dependencies.

    To create a deployment package for a Visual Basic 5.0 application, run the Visual Basic 5.0 Setup Wizard on a system containing only Visual Basic 5.0 so that the appropriate controls are included in your deployment package.


  • For additional information about other potential conflicts, please see the following articles in the Microsoft Knowledge Base:
    Q190253 INFO: VB6 Designers Do Not Work in VB5

    Q190080 PRB: VBCE 5.0 on Same Machine as VB6 Causes Application Error

    Q192934 PRB: Error "The Jet VBA File...Failed to Initialize When Called
  • The following error message displays when you attempt to use the Microsoft Windows Common Controls 5.0 (Comctl32.ocx) in a Visual Basic 5.0 project. The system once had Visual Basic 6.0 installed:
    Could Not Be Loaded - Adding component to project
    This error message occurs when you install a newer version of an ActiveX control, uninstall it, and then install an older version of the same ActiveX control. The registry key for the newer version of the ActiveX control remains in the registry and Visual Basic 5.0 is now trying to use that registry key.

    WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

    For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

    Here are two ways to resolve this issue:

    • Delete the TypeLib Registry Key for the ActiveX Control and then re-register the control using RegSvr32.exe.


    • For additional information on how to delete a registry key and re-register an ActiveX control, please see the following article in the Microsoft Knowledge Base:
      Q217180 HOWTO: Delete and Re-register the TypeLib GUID for an ActiveX Control.
    • Use the Windows Registry Analysis and Correction Utility, RegClean, to resolve registry conflicts.


    • For more information about RegClean, please see the following article in the Microsoft Knowledge Base:

      Q147769 INFO: RegClean 4.1a Description and General Issues
      NOTE: RegClean will only be effective if Comctl32.ocx is deleted from the system before running RegClean.


  • When attempting to create a Visual Basic Application Wizard project in the Visual Basic 6.0 Learning Edition you receive the following message:
    You do not have the proper license to load the VB 98 Application Wizard. You must have the Learning, Professional, or Enterprise edition of Visual Basic installed.
    This is caused by having the Visual Basic 5.0 Control Creation Edition installed on the same system. Please see the following article in the Microsoft Knowledge Base:
    Q220816 BUG: Application Wizard License Not Found


(c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Arsenio Locsin, Microsoft Corporation.


REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

Q190211 PRB: Problems With Visual Basic 5.0 and 6.0 on Same System

Additional query words:

Keywords : kbwizard kbAppSetup kbVBp500 kbVBp600
Version : WINDOWS:5.0,6.0
Platform : WINDOWS
Issue type : kbinfo


Last Reviewed: July 9, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.