The information in this article applies to:
SYMPTOMSMicrosoft Visual Basic 4.0 distributions built using the Setup Wizard will not work properly if created on a system that also has Microsoft Visual Basic Control Creation Edition version 5.0 installed. CAUSE
Microsoft Visual Basic Control Creation Edition 5.0 installs components
that are incompatible with Microsoft Visual Basic 4.0's Setup Wizard. These
components require different runtime components than the earlier Microsoft
Visual Basic 4.0 versions. The new controls that are affected are:
COMCTL32.OCX The files upon which these controls depend are: ASYCFILT.DLL OLEAUT32.DLL OLEPRO32.DLL STDOLE32.TLB Changing the SWDEPEND.INI file for Microsoft Visual Basic 4.0's Setup Wizard usually allows the appropriate files (above) to be included with the distributed diskettes. However, OLEAUT32.DLL is a System file that is commonly in use by the operating system, even with no other applications running. This situation requires a system reboot to update OLEAUT32.DLL properly. The Setup Wizard included with Microsoft Visual Basic 4.0 does not support rebooting. RESOLUTION
There are two possible workarounds for this behavior.
Workaround 1Prior to installing Microsoft Visual Basic Control Creation Edition version 5.0, copy the following components:COMCTL32.OCX to the following folder: C:\Program Files\Microsoft Visual Basic\Setupkit\Kitfil32\sys32 Microsoft Visual Basic 4.0's Setup Wizard always looks at the above folder first when searching for dependent files. Next, when you create distribution disks with Microsoft Visual Basic 4.0's Setup Wizard, follow these steps:
Workaround 2Another workaround is to maintain a pure Microsoft Visual Basic 4.0 system (one without Microsoft Visual Basic Control Creation Edition version 5.0 installed) for the purpose of creating Setup distribution files.STATUSThis behavior is by design. Additional query words:
Keywords : kbVBp400 kbVBp500 kbGrpVB kbhowto |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |