Microsoft KB Archive/120573

{|
 * width="100%"|

WD: List of Fixed Bugs in Word version 6.0c for Windows

 * }

Q120573

-

The information in this article applies to:


 * Microsoft Word for Windows, version 6.0c

-

SUMMARY
Word 6.0c for Windows was created primarily to provide support for Lotus Notes Field Exchange (FX); however, a few problems were also corrected or addressed. This article describes the new Lotus Notes/FX support and problems in Word versions 6.0 and 6.0a for Windows that are corrected in the Word 6.0c upgrade.

If you are experiencing one of the problems listed below or want to take advantage of the added Lotus Notes/FX support, you should obtain Word 6.0c.

WORD 6.0C: NEW FEATURES

 * Support for Lotus Notes Field Exchange (FX) (includes new online Help topics)

WORD 6.0C: FIXED PROBLEMS

 * 1) Some master document problems corrected (includes updated online Help)
 * 2) Word 2.x templates updated and improved for Word 6.0
 * 3) Support for Word 6.0 for the Macintosh PICT graphic format
 * 4) WordBasic errors in Word for the Macintosh running Word for the Macintosh macro that has been edited in Word for Windows
 * 5) Multiple-page table rows print incorrectly (display correctly)
 * 6) Includes Word optimization document: SPEEDUP.DOC
 * 7) Updated file converters and graphics filters

To obtain pre-sales information about new or updated Microsoft products, call the Microsoft Sales Information Center at (800) 426-9400.If you are outside the United States, contact your local subsidiary. To locate your subsidiary, see the Microsoft World Wide Offices Web site at:

"http://www.microsoft.com/worldwide/default.htm" If you experience one of the problems described in this article, contact Microsoft Product Support Services (PSS) at (425) 462-9673.

Support for Lotus Notes Field Exchange (FX)
Word 6.0c supports Lotus Notes/FX and includes extensive online Help about this new functionality.

If Lotus Notes version 3.0 is installed on your computer, the Word Setup program modifies your Notes configuration so Notes can open Word documents. With Word 6.0c, you can import a Word document into Lotus Notes, and you can also export Lotus Notes text in Microsoft Word Rich Text Format (RTF).

Once you embed a Word document in a Lotus Notes form, you can display predefined Word fields. Most of the predefined Word fields that Lotus Notes can display are found in the summary information for the Word document. For example, you can create fields within a Lotus Notes form that display the title and author of the Word document.

You can also create Word bookmarks that Lotus Notes can use as fields. For example, you can define a bookmark that marks some important text in your Word document. Give the bookmark a name using prop_ as a prefix and then use the bookmark name (without the prefix) as a field in a Lotus Notes form or views of the form. The bookmarked text now appears in Lotus Notes without opening the Word document object. If you change the text in either the Word object or Lotus Notes, the change will be reflected in both applications. In other words, changes in Word are reflected in the Lotus Notes field and changes in Lotus Notes field are reflected in the embedded Word object.

For more information about using Lotus Notes with Word 6.0c double-click the Help button on the Standard toolbar, and then type lotus notes.

WORD 6.0 AND 6.0A PROBLEMS CORRECTED IN WORD 6.0C
  Some master document problems corrected (includes updated online Help)

Due to a Windows system limitation, in Word 6.0 or 6.0a, when you save a master document that contains many (usually around 30 or more) subdocuments, one of the following error messages may occur:

Word cannot save or create this file. Make sure the disk is not write protected.

"-or-"

The disk is full or too many files are open.

The File Save operation fails when the supply of available Windows file handles is exhausted. As a safeguard, Word temporarily renames your documents with temporary filenames during the save operation. Normally, the temporary files are then properly renamed back to the original document names once the save operation is complete. When the File Save operation fails due to a lack of Windows file handles, however, one or more of the subdocument temporary files may not get renamed to the original document name. While the subdocument still exists as a temporary file, it appears to be deleted because Word cannot locate it.

IMPORTANT: This problem occurs due to a Windows system file handle limitation. This problem may not occur in Word 6.0 for other operating systems, such as Word 6.0 for the Macintosh.

Word 6.0c partially fixes this problem. In Word 6.0c for Windows, a master document may still exhaust the supply of available Windows file handles. However, when you save, Word 6.0c checks the number of available file handles as it performs the save and displays an error message if it cannot save the next subdocument due to insufficient available file handles. Word then asks if you want to collapse some of the subdocuments into the master document. (This is the same as choosing the Remove Subdocument button on the Master Document toolbar.) If you choose Yes, Word collapses subdocuments into the master document until enough file handles are available to save the master document and the remaining subdocuments. By moving the contents of some subdocuments to the master document, Word prevents the appearance of data loss that may occur in Word 6.0 and 6.0a.

Word collapses subdocuments in the following order:

 Word removes the most deeply nested subdocuments first. Word starts removing subdocuments at the end of the master document and works upward to the beginning. Word removes unsaved subdocuments or subdocuments whose file handles are only referenced first by the subdocument.

Note: If Word 6.0c cannot remove enough subdocuments to successfully save the document, the save operation fails.

Documentation Error: Page 534 of the Word for Windows "User's Guide" incorrectly states that the maximum number of subdocuments is 80. For most systems and most master documents, this maximum is closer to 30 subdocuments, depending on both the state of the system at the time and the complexity of the document. For more information about these settings, please see the following article in the Microsoft Knowledge Base:   Word 2.x letter templates updated and improved for Word 6.0

Word 6.0c includes some of the templates supplied with Word 2.x, converted to Word 6.0 format. These converted letter and memo templates run without the known errors that occur when you run the unconverted Word 2.x templates in Word 6.0. They use the address lists and other custom settings you created in Word 2.x by copying them from the Word 2.x templates into the updated Word 6.0 templates. Below are the names of the converted Word 2.x templates supplied with Word 6.0c:      Template Filename       Description -      ---

LETBLOCK.DOT           Block Letter LETPERSN.DOT           Personal Letter LETMDSEM.DOT           Modified Semi-Block Letter LETMODBK.DOT           Modified Block Letter MEMO2.DOT              Memorandum   Support for Word 6.0 for the Macintosh PICT graphic format

In Word 6.0 and 6.0a for Windows, if you open a Word 6.0 for the Macintosh document that contains a graphic, the following message appears in place of the image: "Use Word 6.0c or later to view Macintosh picture." Word version 6.0 and 6.0a for Windows can neither display nor print a PICT graphic in a converted Word 6.0 for the Macintosh document. Word version 6.0c correctly displays and prints PICT graphics.

For more information, please see the following articles in the Microsoft Knowledge Base:   WordBasic Errors in Word for the Macintosh Running Word for the Macintosh Macro that Has Been Edited in Word for Windows

The following problem is partially fixed in Word 6.0c:

If you edit and save a cross-platform macro in Word 6.0 and 6.0a for Windows, Word for Windows deletes Macintosh-specific commands (such as MacID$) from the macro. For example, if you open and edit, then save changes to the following cross-platform macro in Word 6.0 or 6.0a for Windows, <pre class="CODESAMP">   Sub MAIN a$ = MacID$("TEXT") End Sub the macro appears as shown below when you open it in Word for the Macintosh (notice that the Macintosh-specific MacID$ command is missing): <pre class="CODESAMP">   Sub MAIN a$ = ("TEXT") End Sub In other words, Word 6.0 and 6.0a for Windows delete unknown Macintosh commands from your macros when you edit, or "dirty," them in Word 6.0 and 6.0a for Windows.

Word 6.0c does not delete unknown commands from your macros when you edit them. Instead of deleting the Macintosh-specific command, Word 6.0c replaces it with an "Unrecognized_Command" string, or token. For example, if you create the following macro in Word 6.0 or 6.0a for Windows, <pre class="CODESAMP">   Sub Main a$ = MacID$("TEXT") End Sub save and close the macro, and then re-open it in Word 6.0c for Windows, the macro will be changed to the following: <pre class="CODESAMP">   Sub Main a$ = Unrecognized_Statement33134("TEXT") End Sub Note: "33134" is the token identification number for the "MacID$" command. Word 6.0c for Windows does not automatically replace the token ID with the Macintosh-specific WordBasic token command. To restore the Macintosh token IDs so your macro will run without errors in Word for the Macintosh, you must "dirty" the macro in Word for the Macintosh (that is, you must change the macro before you run it).

In other words, while Word 6.0c for Windows no longer deletes any unrecognized commands, it still does not automatically change the token IDs back to Macintosh-specific WordBasic commands in your macro. To work around this limitation when you create a cross-platform macro in Word 6.0c for Windows, be sure to dirty the macro once in Word 6.0 for the Macintosh. You can then distribute your cross-platform macro, and it will run without missing-token errors. </li> Multiple-Page Table Rows Print Incorrectly (Display Correctly)

The following Word 6.0 and 6.0a for Windows problem is corrected in Word 6.0c:

In Word 6.0 and 6.0a, text from a table row that spans a page break may print again in the bottom margin of the preceding page. Specifically, if one or more cells in a table row span a page break and if the table row also contains a cell on the right side of the page-spanning cell that is blank or does not span the page break, text from the following page sometimes prints in the bottom margin. For example, if cell B spans the page break between pages 3 and 4 and cell C is only one line long on page 3, the column B text at the top of page 4 also prints in the bottom margin of page 3.

IMPORTANT: Word 6.0c does not address a similar problem that you can resolve by turning off the Background Printing option. To determine whether you need Word 6.0c, turn off Background Printing, and then print your document. If text continues to print in the bottom margin of the previous page, you should obtain Word 6.0c. If the problem no longer occurs after you turn off Background Printing, your problem is not addressed in Word 6.0c.

This problem does not occur in Word 6.0 for the Macintosh.

For more information, please see the following article in the Microsoft Knowledge Base:</li> Includes Word Optimization Document: SPEEDUP.DOC.

Word 6.0c includes a new document, SPEEDUP.DOC, which contains the recently published "How to Optimize the Performance of Word 6.0" Application Note (WD1015). SPEEDUP.DOC describes how you can increase the operating speed of Word 6.0 for Windows when it is running under Microsoft Windows version 3.1 or Windows for Workgroups version 3.1 or 3.11. (Word Setup installs SPEEDUP.DOC in the Word for Windows program directory.)</li> Updated File Converters and Graphics Filters.

Word 6.0c provides the following updated file converters:

<ul> WordPerfect and DisplayWrite.</li> Word 6.0 for Windows. (This is the converter other applications use to read Word 6.0 documents.)</li> RFT-DCA.</li></ul>

For more information about updated file converters, please see the following article in the Microsoft Knowledge Base:</li></ol>

Word 6.0c includes updated .BMP, .TIF, .PCX, .GIF, and .TGA graphics filters. No new graphics filters are provided. The table below lists the major problems fixed by the updated graphics filters.

<pre class="FIXEDTEXT"> Graphics           Problem Fixed in Filter Filter             Supplied with Word 6.0c ---

.GIF               Inserted CompuServe GIF(.GIF) graphic file displays (GIFIMP.FLT)       as solid blackbox in Word 6.0 and 6.0a. With Word 6.0c, .GIF files display and print correctly as                    pictures.

.TIF               If a Tagged Image File Format (.TIF) graphic file is (TIFFIMP.FLT)       both compressed and smaller than 500 kilobytes, the following error may occur when you insert it in                    Word 6.0 or 6.0a:

This graphics file may be damaged and cannot be converted.

This problem may not occur if the graphic file is                    compressed and larger than 500K or uncompressed and smaller than 500K. The .TIF graphics filter supplied with Word 6.0 and 6.0a has problems reading file sizes less than 500K. The above error does not occur when you use the .TIF graphic filter supplied with Word 6.0c.

.TIF               Some .TIF files display in reverse or inverted colors (TIFFIMP.FLT)      (for example, black displays as white and white as                     black), or the following error occurs:

This graphics file may be damaged and cannot be converted.

The Word 6.0c .TIF filter imports these .TIF pictures correctly.

.PCX               The following error may occur when you insert some (PCXIMP.FLT)       small PC Paintbrush (.PCX) graphics files in Word 6.0 or 6.0a:

This file may be damaged or corrupted.

Specifically, this error occurs using .PCX files, such as the following, that were created using third-party utilities that generate an incorrect .PCX file header: <pre class="FIXEDTEXT">                    ClickArt files (by T/Maker Christian Images                     Library, [415] 962-0195):

CROSS_28.PCX CROSS_27.PCX CROSS_91.PCX CROSS_03.PCX TEXAS.PCX WYOMING.PCX PENN.PCX CALIF.PCX

Sampler Images Disk files (by Parsons Technology,                    [319] 395-7314):

TORCH.PCX FIDDLER.PCX MEDICALS.PCX

When you use the .PCX filter supplied with Word 6.0c, to import these files, no errors occur and the pictures display correctly.

All German Word for If you insert a .PCX picture after you install any of Windows Graphics   the graphics filters supplied with the German Filters            localized version of Word 6.0 or 6.0a for Windows, the Cancel button in the conversion status dialog box is partially missing. (The conversion status dialog                    box displays the percentage completed for the graphic                     conversion.) Additional query words: buglist fixlist6.0c word6 winword new custserve fix list of bugs confirmed fixes

Keywords : kbmacro kbofficeprog

Issue type :

Technology : kbWordSearch kbWordWSearch