WD2000: InsertSymbol Result Not Translated Between Macintosh and ANSI (201967)
The information in this article applies to:
This article was previously published under Q201967 SYMPTOMS
If you run a Microsoft Visual Basic for Applications macro (Sub procedure)
that inserts a character, a different character may be inserted when the
macro is run on the Macintosh than when it is run on Windows.
CAUSE
Word currently does not support conversion of Macintosh CharNum values to
equivalent ANSI values, and vice versa.
When a Visual Basic for Applications macro that includes the InsertSymbol
method is exchanged between Word 98 Macintosh Edition or later versions for
the Macintosh and Word 97 or later versions for Windows, the numeric value
of the CharNum or CharacterNumber command is not translated from its
Macintosh character set value to its ANSI equivalent, and vice versa.
WORKAROUNDMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Edit the macro on the target platform, replacing the character value with
the value that gives correct results. In the following example, replace the
number 203 with 192. (ANSI 192, Capital A Grave, is the equivalent of
Macintosh character 203.)
The following macro statements insert the Capital A Grave character:
' Word for Windows statement
Selection.InsertSymbol CharacterNumber := 192, Font:= "(normal text)"
' Macintosh Word statement
Selection.InsertSymbol CharacterNumber := 203, Font:= "(normal text)"
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. REFERENCESFor additional information about getting help with Visual Basic for Applications, please see the following article in the
Microsoft Knowledge Base:
ARTICLE-ID: 163435
TITLE : VBA: Programming Resources for Visual Basic for Applications
Modification Type: | Major | Last Reviewed: | 6/17/2005 |
---|
Keywords: | kbbug kbdtacode kbmacroexample kbnofix KB201967 |
---|
|