WD97: WordBasic Object Returns Incorrect ASCII Number For Symbol

 Last reviewed: February 11, 1998
Article ID: Q165604
The information in this article applies to:
  • Microsoft Word 97 for Windows

SYMPTOMS

The value returned for a symbol character in a WordBasic macro is different from the value returned for the same symbol when you convert the WordBasic macro into a Visual Basic for Applications macro.

For example, the WordBasic macro returns a value of 183 for a bullet character in the Symbol font, but the Visual Basic for Applications macro returns the value of 63 for the same character and font.

CAUSE

Characters in the Symbol font are stored in Unicode. The value used is a subset of Unicode character mapping.

MORE INFORMATION

For more information about returning character values, while in the Visual Basic for Applications Editor click the Office Assistant, type "Asc," click Search, and then click to view "ASC Function."

For more information about Unicode, visit the Unicode Web site at: 

   http://www.unicode.org
NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If Microsoft Visual Basic Help is not installed on your computer, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q120802
   TITLE     : Office: How to Add/Remove a Single Office Program or
               Component

Additional query words: 97 word8 word97 8.0 8.0 vb vba vbe
Keywords : kbmacro kbwordvba
Version : 97
Platform : WINDOWS
Hardware : x86
Issue type : kbprb
Solution Type : kbcode

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: February 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.