Microsoft KB Archive/177971

= WD97: Type Mismatch Error Running Converted WordBasic Macro =

Article ID: 177971

Article Last Modified on 1/22/2007

-

APPLIES TO


 * Microsoft Word 97 Standard Edition

-



This article was previously published under Q177971





SYMPTOMS
When you run a macro that was converted from WordBasic to Microsoft Visual Basic for Applications, you receive the following error message:

Type Mismatch Error



CAUSE
If you converted a WordBasic macro that contains statements similar to the following: x = Val(FontSize) the converted code may appear as: x = WordBasic.Val(WordBasic.FontSize) This converted statement causes the macro to halt with the "Type Mismatch" error message.



RESOLUTION
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals 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 needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

To resolve this problem, remove "WordBasic." from the Val function as in the following example: x = Val(WordBasic.FontSize) -or-

Convert the statement to the Visual Basic equivalent: x = Selection.Font.Size



STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

