Article ID: 826287
Article Last Modified on 10/7/2005
APPLIES TO
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
- Microsoft Visual Basic 6.0 Learning Edition
SYMPTOMS
When you run an application that uses the ImageList control from Microsoft Windows Common Controls 6.0 (Mscomctl.ocx) on a computer that is running Microsoft Windows XP or later, you may experience the following problems:
- Images in the application do not appear.
- Controls that use the ImageList control may stop functioning correctly.
CAUSE
These problems are caused by an update of the ImageList structure in the version of the Comctl32.dll file that is included with Windows XP.
You experience these problems if one of the following behaviors occurs:
- The application calls ImageList APIs such as ImageList_ReplaceIcon from Comctl32.dll.
- The application calls the SendMessage API when the application uses ImageList messages such as TB_GETIMAGELIST or LVM_SETIMAGELIST.
The application passes the handle of the ImageList control to these API calls. (The handle is obtained through the hImageList property.) This handle points to the old ImageList structure. However, the API call treats the handle as though it pointed to the new ImageList structure that is defined in Comctl32.dll. Because of this behavior, the image in the ImageList structure is manipulated incorrectly. Therefore, the image is not valid in the application.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Visual Studio 6.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
194022 Visual Studio 6.0 service packs, what, where, why
This problem is fixed in the update for the Microsoft Visual Basic 6.0 Common Controls. To obtain this update, visit the following Microsoft Web site:
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 6.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------ 05-Aug-2003 02:34 6.1.97.64 1,074,688 Mscomctl.ocx
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio 6.0 Service Pack 6.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbfix kbvbp600fix KB826287
