Helv and Tms Rmn FontNames Not Available in Windows 3.1

Last reviewed: June 21, 1995
Article ID: Q84470
The information in this article applies to:
  • Standard and Professional Editions of Microsoft Visual Basic for Windows, versions 2.0 and 3.0
  • Microsoft Visual Basic programming system for Windows, version 1.0

SUMMARY

Helv and Tms Rmn are no longer listed in the Settings box of the Properties bar as selections for the FontName property in Visual Basic under Windows version 3.1. By default, Windows version 3.1 maps the fonts Helv and Tms Rmn to MS Sans Serif and MS Serif, respectively.

MORE INFORMATION

Visual Basic uses Helv as the default setting for the FontName property of forms and controls. That font is still the default setting for FontName in Visual Basic, even though it is no longer a system font in Windows version 3.1. Helv and Tms Rmn are no longer listed in the drop-down list box in the Properties bar.

In Windows version 3.1, Helv is mapped to MS Sans Serif and Tms Rmn is mapped to MS Serif by default. This appears in the [FontSubstitutes] section of the WIN.INI file. Therefore, FontName can still be set to Helv or Tms Rmn at run-time without producing any errors, even though they are no longer available. Windows will instead use the existing fonts to which they are mapped.


Additional reference words: 1.00 2.00 3.00
KBCategory: kbenv kbprg
KBSubcategory: EnvtDes


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 21, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.