DOCUMENT:Q161344 13-AUG-1997 [vbwin] TITLE :PRB: Problems Using Visual Basic 5.0 and 4.0 on Same System PRODUCT :Microsoft Visual Basic for Windows PROD/VER:4.0 5.0 OPER/SYS:WINDOWS KEYWORDS:vb432 VB4WIN vb5all VBKBComp VBKBSetup VBKBWiz kbsetup kbtool kbprb ====================================================================== ------------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Learning, Professional and Enterprise Editions, for Windows, version 5.0 - Microsoft Visual Basic Standard, Professional and Enterprise Editions, 32-bit only, for Windows, version 4.0 -------------------------------------------------------------------------- SYMPTOMS ======== If Microsoft Visual Basic version 5.0 and Microsoft Visual Basic version 4.0 32-bit are installed on the same machine, inconsistent behavior is observed when using Microsoft Visual Basic 4.0. CAUSE ===== Microsoft Visual Basic version 5.0 is designed to replace Microsoft Visual Basic version 4.0 and to upgrade the earlier components (including .OCX controls) to newer versions. Maintaining both versions of Visual Basic on the same machine is not recommended because many of the new version 5.0 features and components are not supported in version 4.0. The following Microsoft Visual Basic 4.0 32-bit files are replaced with updated Microsoft Visual Basic 5.0 components: acmsetup.exe msmask32.ocx p2irdao.dll comctl32.ocx mssetup.dll p2sodbc.dll comdlg32.ocx msvcrt20.dll picclp32.ocx compress.exe msvcrt40.dll richtx32.ocx crpe32.dll odbc16gt.dll scp32.dll crxlat32.dll odbc32.dll sqlsrv32.dll crystl32.ocx odbc32gt.dll tabctl32.ocx ctl3d32.dll odbcad32.exe u2ddisk.dll dbgrid32.ocx odbccp32.cpl u2dmapi.dll dblist32.ocx odbccp32.dll u2fcr.dll dbnmpntw.dll odbccr32.dll u2fdif.dll drvssrvr.hlp odbcint.dll u2frec.dll ds16gt.dll ODBCJI32.DLL u2frtf.dll ds32gt.dll ODBCJT32.DLL u2fsepv.dll mci32.ocx odbcstf.dll u2ftext.dll mfc40.dll ODBCTL32.DLL u2fwks.dll mscomm32.ocx P2BBND.DLL u2fxls.dll mscpxl32.dll p2bdao.dll vbajet32.dll msmapi32.ocx p2ctdao.dll vbskco32.dll These components behave differently than the components released with the 32-bit version of Microsoft Visual Basic 4.0. RESOLUTION ========== Create a dual-boot system in which one boot of the operating system will be installed with Microsoft Visual Basic 4.0 32-bit and the other will be installed with Microsoft Visual Basic 5.0. See the REFERENCES section of this article for more information. STATUS ====== This is the intended behavior of Microsoft Visual Basic 5.0. MORE INFORMATION ================ NOTE: This information does not apply to the Microsoft Visual Basic 5.0 Control Creation Edition. The Microsoft Visual Basic 5.0 Control Creation Edition may be installed in tandem with Microsoft Visual Basic 4.0 (32-bit) releases. For additional information concerning Setup issues with Microsoft Visual Basic 5.0 Control Creation Edition, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q160968 TITLE : PRB: Setup Wizard Fails After Installing VB5CCE REFERENCES ========== For additional information, please see the following articles in the Microsoft Knowledge Base: ARTICLE–ID: Q169979 TITLE : INFO: Visual Basic 5.0 Frequently Asked Questions (FAQ) ARTICLE-ID: Q153762 TITLE : Setting Up Dual Boot After Installing Windows NT ARTICLE-ID: Q155034 TITLE : Dual-Booting Between Windows NT Workstation 4.0 & Windows 95 ARTICLE-ID: Q132733 TITLE : Upgrading to Windows 95 Setup Questions and Answers ====================================================================== Keywords : vb432 VB4WIN vb5all VBKBComp VBKBSetup VBKBWiz kbsetup kbtool kbprb Version : 4.0 5.0 Platform : WINDOWS Issue type : kbprb ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1997.