I've had some problems recently with controls supplied with the VB distribution complaining that I'm not licensed to use them in a development environment - which I am.<br>
<br>
This is a VB bug - the fix is a little utility called VBCMPFIX and the readme file is below. Seems ok, got me running anyway; it's available from <br>
Regards<br>
<br>
Mike<br>
---<br>
README.TXT For VBCMPFIX.EXE Utility File<br>
<br>
What VBCMPFIX Does<br>
------------------<br>
VBCMPFIX is designed to make sure that the controls and components included with Visual Basic 5.0 are installed properly. VBCMPFIX will detect and fix the install problems for the following editions of Visual Basic 5.0:<br>
<br>
Visual Basic 5.0 Enterprise Edition<br>
Visual Basic 5.0 Professional Edition<br>
Visual Basic 5.0 Learning Edition<br>
Visual Basic 5.0 Control Creation Edition<br>
<br>
VBCMPFIX does not require any Service Packs installed to use, however upgrading to the latest Service Pack is always recommended. The latest service pack is available at:<br>
<br>
<br>
<br>
List Of Components VBCMPFIX Will Fix<br>
------------------------------------<br>
<br>
Depending upon which edition of Visual Basic 5.0 you have installed, VBCMPFIX will fix your installation so that controls and components that come with VB5 work in the VB5 design environment. VBCMPFIX.EXE works ONLY with the components listed below, and will not affect any other third party controls you might be having problems with, or fix problems with any controls in the \Tools\Controls directory on the Visual Basic 5.0 CD.<br>
<br>
Component List Ent Pro Lrn CCE<br>
--------------------------------------------------------------------------<br>
Microsoft Data Bound List Control X X X <br>
Auto Connection Manager (AddIn) X X<br>
Microsoft Tabbed Dialog Control X X X<br>
Microsoft Winsock Control X X<br>
Microsoft Comm Control X X<br>
Microsoft RemoteData Control X<br>
Microsoft Common Dialog Control X X X X<br>
Microsoft Data Bound Grid Control X X X<br>
Microsoft Windows Common Controls (1) X X X X<br>
Microsoft PictureClip Control X X<br>
Microsoft Flexgrid Control X X X<br>
Microsoft Internet Transfer Control X X<br>
Microsoft Chart Control X X<br>
Microsoft MAPI Controls X X<br>
Microsoft Windows Common Controls (2) X X<br>
VB T-SQL Debugger (AddIn) X<br>
Microsoft UserConnection <br>
(ActiveX Designer) X<br>
Microsoft Remote Data Object 2.0 X<br>
Microsoft Multimedia Control X X<br>
Microsoft Masked Edit Control X X<br>
Microsoft Rich TextBox Control X X<br>
Microsoft SysInfo Control X X<br>
Data Access Objects 3.50 <br>
Object Library X X<br>
<br>
How To Use<br>
----------<br>
<br>
VBCMPFIX is very simple to use. Run the self extracting VBC.EXE program, which will extract two files: <br>
<br>
VBCMPFIX.EXE<br>
ReadMe.Txt<br>
<br>
Double click on VBCMPFIX.EXE from the Windows Explorer, or run it from the command line.<br>
<br>
When VBCMPFIX launches, it will automatically detect which version of Visual Basic you have installed on your system. If you do not have Visual Basic installed, it will not allow you continue.<br>
<br>
After it detects your version of Visual Basic, you can "Fix Install" or "Quit". Choosing "Fix Install" will update your system so that the controls and components that come with your edition of Visual Basic will work. The controls and components that are fixed is dependent upon the edition of Visual basic 5.0 you have installed.<br>
<br>
After you have done this, close the utility and reboot your system. After rebooting, launch Visual Basic 5 and try using any controls you were having problems with.<br>
<br>
Known Issues<br>
------------<br>
<br>
Users of Internet Explorer 4.x might notice that their desktop goes crazy after running VBCMPFIX.EXE. Bitmaps might become black and/or colors will be strange. Rebooting will solve this problem.<br>
<br>
If you still cannot use controls after running VBCMPFIX.EXE, please contact Microsoft Visual Basic Technical Support. Re-run VBCMPFIX.EXE and write down the build number of the utility (given in the about box), and have that handy in case they ask for it. VBCMPFIX will not work on systems that have certain security settings, and Microsoft Visual Basic Technical Support will assist you in resolving this problem.<br>
<br>
If you install Visual Basic on a network, sometimes security settings will carry over, and your system will not let VBCMPFIX.EXE to run correctly.<br>
<br>
Updated : 02/28/98<br>
Written by : Robert Young/Israel Burman/Robert Jacik<br>
<br>
This is a VB bug - the fix is a little utility called VBCMPFIX and the readme file is below. Seems ok, got me running anyway; it's available from <br>
Regards<br>
<br>
Mike<br>
---<br>
README.TXT For VBCMPFIX.EXE Utility File<br>
<br>
What VBCMPFIX Does<br>
------------------<br>
VBCMPFIX is designed to make sure that the controls and components included with Visual Basic 5.0 are installed properly. VBCMPFIX will detect and fix the install problems for the following editions of Visual Basic 5.0:<br>
<br>
Visual Basic 5.0 Enterprise Edition<br>
Visual Basic 5.0 Professional Edition<br>
Visual Basic 5.0 Learning Edition<br>
Visual Basic 5.0 Control Creation Edition<br>
<br>
VBCMPFIX does not require any Service Packs installed to use, however upgrading to the latest Service Pack is always recommended. The latest service pack is available at:<br>
<br>
<br>
<br>
List Of Components VBCMPFIX Will Fix<br>
------------------------------------<br>
<br>
Depending upon which edition of Visual Basic 5.0 you have installed, VBCMPFIX will fix your installation so that controls and components that come with VB5 work in the VB5 design environment. VBCMPFIX.EXE works ONLY with the components listed below, and will not affect any other third party controls you might be having problems with, or fix problems with any controls in the \Tools\Controls directory on the Visual Basic 5.0 CD.<br>
<br>
Component List Ent Pro Lrn CCE<br>
--------------------------------------------------------------------------<br>
Microsoft Data Bound List Control X X X <br>
Auto Connection Manager (AddIn) X X<br>
Microsoft Tabbed Dialog Control X X X<br>
Microsoft Winsock Control X X<br>
Microsoft Comm Control X X<br>
Microsoft RemoteData Control X<br>
Microsoft Common Dialog Control X X X X<br>
Microsoft Data Bound Grid Control X X X<br>
Microsoft Windows Common Controls (1) X X X X<br>
Microsoft PictureClip Control X X<br>
Microsoft Flexgrid Control X X X<br>
Microsoft Internet Transfer Control X X<br>
Microsoft Chart Control X X<br>
Microsoft MAPI Controls X X<br>
Microsoft Windows Common Controls (2) X X<br>
VB T-SQL Debugger (AddIn) X<br>
Microsoft UserConnection <br>
(ActiveX Designer) X<br>
Microsoft Remote Data Object 2.0 X<br>
Microsoft Multimedia Control X X<br>
Microsoft Masked Edit Control X X<br>
Microsoft Rich TextBox Control X X<br>
Microsoft SysInfo Control X X<br>
Data Access Objects 3.50 <br>
Object Library X X<br>
<br>
How To Use<br>
----------<br>
<br>
VBCMPFIX is very simple to use. Run the self extracting VBC.EXE program, which will extract two files: <br>
<br>
VBCMPFIX.EXE<br>
ReadMe.Txt<br>
<br>
Double click on VBCMPFIX.EXE from the Windows Explorer, or run it from the command line.<br>
<br>
When VBCMPFIX launches, it will automatically detect which version of Visual Basic you have installed on your system. If you do not have Visual Basic installed, it will not allow you continue.<br>
<br>
After it detects your version of Visual Basic, you can "Fix Install" or "Quit". Choosing "Fix Install" will update your system so that the controls and components that come with your edition of Visual Basic will work. The controls and components that are fixed is dependent upon the edition of Visual basic 5.0 you have installed.<br>
<br>
After you have done this, close the utility and reboot your system. After rebooting, launch Visual Basic 5 and try using any controls you were having problems with.<br>
<br>
Known Issues<br>
------------<br>
<br>
Users of Internet Explorer 4.x might notice that their desktop goes crazy after running VBCMPFIX.EXE. Bitmaps might become black and/or colors will be strange. Rebooting will solve this problem.<br>
<br>
If you still cannot use controls after running VBCMPFIX.EXE, please contact Microsoft Visual Basic Technical Support. Re-run VBCMPFIX.EXE and write down the build number of the utility (given in the about box), and have that handy in case they ask for it. VBCMPFIX will not work on systems that have certain security settings, and Microsoft Visual Basic Technical Support will assist you in resolving this problem.<br>
<br>
If you install Visual Basic on a network, sometimes security settings will carry over, and your system will not let VBCMPFIX.EXE to run correctly.<br>
<br>
Updated : 02/28/98<br>
Written by : Robert Young/Israel Burman/Robert Jacik<br>
