Microsoft KB Archive/127876

= WD6X: Word 6.0 BatchConversion Macro Exports Incorrect Format =

Article ID: 127876

Article Last Modified on 7/13/2007

-

APPLIES TO


 * Microsoft Word 6.0 for Macintosh
 * Microsoft Word 6.01 for Macintosh
 * Microsoft Word 6.01 for Macintosh

-



This article was previously published under Q127876



SYMPTOMS
The BatchConversion macro included with Word 6.x exports some file formats incorrectly. The following is a list of export options and what Word actually exports a Word document to when these export options are selected:   Export option               Actual export result -

Rich Text Format           Text Only Text Only with Linebreaks  Word Document Template Text Only                  Word Document Documents you select to be exported as "Rich Text Format," but that are actually exported as "Text Only," receive the file type "TEXT." They therefore appear with an icon normally assigned to a file exported as "Text Only."

Documents you select to be exported as "Text Only with Line Breaks," but that are actually exported as "Word Document Templates," receive the file type "WTBN" and appear on your system with a Word document template icon.



WORKAROUND
To batch export documents as "Text Only with Line Breaks," instead select the "MS-DOS Text with Line Breaks" BatchConversion macro export option.

To batch export documents as "Text Only," instead select the "Rich Text Format" BatchConversion macro export option.

To export as RTF format, you will need to export documents manually without use of the BatchConversion macro.



STATUS
Microsoft has confirmed this to be a problem in the BatchConversion macro supplied with Word versions 6.x for the Macintosh. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: batch conversion macro convert converts converted converting converter converters text with line breaks

Keywords: kbbug kbmacro KB127876

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.