WD: Continuous Section Break in AutoText Changed to Page Break

• Microsoft Word for Windows, versions 1.0, 1.1, 1.1a, 2.0, 2.0a, 2.0a-CD, 2.0b, 2.0c, 6.0, 6.0a, 6.0c
• Microsoft Word for Windows 95, version 7.0, 7.0a
• Microsoft Word for Windows NT, version 6.0
• Microsoft Word for the Macintosh, versions 6.0, 6.0.1

SUMMARY

When you copy and paste a selection that contains a continuous section break, the original section break turns into a new page section break while a continuous section break is inserted at the point that you pasted information. The same behavior occurs when you insert an AutoText entry that contains a continuous section break.

The format of odd and even section breaks is retained when copied and used for AutoText.

WORKAROUND

After pasting or inserting an AutoText entry containing a continuous section break, manually change the section break formatting from Next Page to Continuous:

Word 6.x and 7.x

1. Position the insertion point before the new section break.

2. On the File menu, click Page Setup.

3. On the Layout tab, change Section Start from New Page to Continuous.

4. Click OK.

Word 2.x

1. Position the insertion point after the last section break inserted by the Glossary entry.

2. On the Format menu, click Section Layout.

3. Click Continuous and click OK.

Word 1.x

1. Position the insertion point after the last section break inserted by the Glossary entry.

2. On the Format menu, click Section.

3. Select the No Break option and click OK.

STATUS

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

MORE INFORMATION

When the section break changes from a continuous to a new page section break, this can affect other section formatting and layout appearance. For example, if the AutoText contains column-formatted text and section breaks, the formatting may appear to be lost when the AutoText entry is inserted into a document. Use the same workarounds listed above to correct the problem.