Microsoft KB Archive/171503: Difference between revisions
m (Text replacement - "[[mk:@MSITStore:kbvstud.chm::/Source/vstudio/q" to "[[../") |
m (Text replacement - "&" to "&") |
||
Line 22: | Line 22: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
Setting the ForeColor property of an object (such as a form or a PictureBox) at design-time to a color other than a system-defined color (a color that starts with & | Setting the ForeColor property of an object (such as a form or a PictureBox) at design-time to a color other than a system-defined color (a color that starts with &h8), causes memory leak in the GDI resources when the object is shown or hidden. This problem does not occur if the property is set during run-time. | ||
<br /> | <br /> |
Latest revision as of 12:29, 21 July 2020
The information in this article applies to:
SYMPTOMSSetting the ForeColor property of an object (such as a form or a PictureBox) at design-time to a color other than a system-defined color (a color that starts with &h8), causes memory leak in the GDI resources when the object is shown or hidden. This problem does not occur if the property is set during run-time.
RESOLUTIONThe workaround for this bug is to obtain Visual Basic 5.0 Service Pack 2 or leave/set the initial ForeColor property for the object to a system-defined color at design-time and set the desired ForeColor of the object at run- time. For example, the ForeColor property could be set to the desired color in the Form_Load event.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.
For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
Additional query words: Keywords : kbVBp500 kbVS97sp2fix kbGrpVB kbvbp500sp2fix |
Last Reviewed: January 5, 2000 |