PRB: Source Control Tool Shows Font Property Deleted on Check-in (202145)
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual SourceSafe for Windows 4.0
- Microsoft Visual SourceSafe for Windows 4.0a
- Microsoft Visual SourceSafe for Windows 5.0
- Microsoft Visual SourceSafe for Windows 6.0
This article was previously published under Q202145 SYMPTOMS
When you use a source code control tool such as Visual SourceSafe on a Visual Basic project, .frm files appear to lose font information for controls.
CAUSE
If a control's font matches the font of the parent form exactly, the font blocks are optimized out of the property definitions. When Visual Basic loads a control that does not contain a font block, the font property of the control is set to the font that is used by the control's parent form.
RESOLUTION
You can safely ignore a difference report that shows a missing font.
To avoid the problem, do one of the following: - Set the Font property of the Form to a font or font size that is not used by the controls on the form.
- Set the Font property of each control at run time.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 12/11/2003 |
---|
Keywords: | kbIDEProject kbprb KB202145 |
---|
|