Please Note: This article is written for users of the following Microsoft Word versions: 2007, 2010, 2013, 2016, 2019, and Word in Office 365. If you are using an earlier version (Word 2003 or earlier), this tip may not work for you. For a version of this tip written specifically for earlier versions of Word, click here: Table Header Rows after a Manual Page Break.
Ed had his table set up the way he wanted, with a couple of rows repeated at the top of each page. He ran into a problem, however, when he inserted a manual page break in the middle of the table. When he did, the formerly repeating rows no longer repeated at the top of the table.
The reason for this is rather simple—when you insert a page break into a table you are, in reality, splitting the table into two separate tables. The rows that were repeating are no longer in the new table, but in the original table.
To get around this problem, don't insert a manual page break in the table to force a row to a new page. Instead, use this formatting approach:
Figure 1. The Line and Page Breaks tab of the Paragraph dialog box.
Now the row will always start at the beginning of a new page, your table is not "broken" into two parts, and your desired rows will still repeat at the top of each page.
WordTips is your source for cost-effective Microsoft Word training. (Microsoft Word is the most popular word processing software in the world.) This tip (13094) applies to Microsoft Word 2007, 2010, 2013, 2016, 2019, and Word in Office 365. You can find a version of this tip for the older menu interface of Word here: Table Header Rows after a Manual Page Break.
Comprehensive VBA Guide Visual Basic for Applications (VBA) is the language used for writing macros in all Office programs. This complete guide shows both professionals and novices how to master VBA in order to customize the entire Office suite for their needs. Check out Mastering VBA for Office 2010 today!
Can you put a numbered outline in a table? Yes, you can. But Word is rather prickly when it comes to using the keyboard ...
Discover MoreNeed to jump from one end of a table row to another? Word provides a couple of handy shortcuts that can make this type of ...
Discover MorePress the Tab key in a table, and Word dutifully moves to the next cell in that table. Press it in the last cell of a ...
Discover MoreFREE SERVICE: Get tips like this every week in WordTips, a free productivity newsletter. Enter your address and click "Subscribe."
2018-09-17 18:33:25
Matt
I do it on 2016, and most of my document disappears. Several pages are gone and I can still scroll over the grey background. I waited a few minutes to let the computer process things (12GB RAM/SSHD), and I gave up and closed the problem to restart with a saved version. This happened twice.
2016-06-27 19:23:42
Michelle
Ditto - it is not working for 2010
2016-02-26 09:27:06
Thelma
Worked ok for me in 2010. Thanks.
2015-10-19 08:50:29
ReadsStuff
It works in later versions of Word (both 2010 and 2013.
1) Do not do a manual page break, forget about that. If you have one in your table, remove it.
2) Insert your cursor into the first cell in the row you want to appear after the page break, check the box for "page break before," and voila, it works.
2015-09-11 08:36:34
Alan Fisk
I tried this in Word 2010 and it had no effect whatsoever.
2015-05-18 13:32:18
CJShank
Can't get it to work in Word 2010.
Got a version of Word that uses the ribbon interface (Word 2007 or later)? This site is for you! If you use an earlier version of Word, visit our WordTips site focusing on the menu interface.
FREE SERVICE: Get tips like this every week in WordTips, a free productivity newsletter. Enter your address and click "Subscribe."
Copyright © 2021 Sharon Parq Associates, Inc.
Please Note:
This article is written for users of the following Microsoft Word versions: 2007, 2010, 2013, 2016, 2019, and Word in Office 365. If you are using an earlier version (Word 2003 or earlier), this tip may not work for you. For a version of this tip written specifically for earlier versions of Word, click here: 
Comments