WD: Hyphens (Dashes) Not Displayed in Form Field Number (122650)



The information in this article applies to:

  • Microsoft Word for Windows 6.0
  • Microsoft Word for Windows 6.0a
  • Microsoft Word for Windows 6.0c
  • Microsoft Word for Windows NT 6.0
  • Microsoft Word for Windows 95
  • Microsoft Word for Windows 95 7.0a
  • Microsoft Word for the Macintosh 6.0
  • Microsoft Word for the Macintosh 6.0.1
  • Microsoft Word for the Macintosh 6.0.1a

This article was previously published under Q122650

SYMPTOMS

When you modify a text form field's number format to include hyphens, the hyphens are not displayed in the form field result.

For example, if you want to format a form field to display a phone number formatted as
   206-555-1234
				
using the number format
   ###-###-####
				
the result is:
   206 555 1234.
				

WORKAROUND

To work around this problem, use the appropriate method for your version of Word.

Word for the Macintosh

Press OPTION+HYPHEN.

Word for Windows

Modify the number format of the form field using any of the following methods. (To locate the Number Format option, unprotect your formfield document and double-click the form field.)

Method 1:

Place apostrophes around the hyphens.

Method 2:

Enter the hyphen using ALT+0173. You must type the 0173 on the numeric keypad.

Method 3:

Press CTRL+Num Pad HYPHEN.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Word 97 and Word 98 Macintosh Edition.

MORE INFORMATION

You can edit form fields in Word by double-clicking the form field. In the text form field dialog box, click Number in the Type list and type the correct number format in the Number Format box.

NOTE: If you try to round-trip through the form fields, you may get the following error message, and the insertion point does not move to the next form field:
A valid number is required.
You must retype the number to exit the field.

Modification Type:MinorLast Reviewed:8/16/2005
Keywords:kbbug kberrmsg kbfield kbfix KB122650