Forum Discussion
Keep with next - if the next text is table does not work anymore
In a quick test, I observed nothing strange here, using a built-in heading style and a table immediately below the heading paragraph.
Did you make sure that there were no blank paragraphs between the heading and the first table row? Click the ¶ icon on the Home tab to view all nonprinting marks.
If you want to, you can share a sample document which illustrates what you see.
In the web browser version of Word, the display is often less reliable. The reading view is more accurate.
Here, I am not seeing a glitch when I open the document in the full version of Word (version 2202, Office 2021, running under Windows 11). Deleting/adding a paragraph mark on the first page will move the title + the table back and forth between the pages in the expected manner.
yes, the same document behaves normally in the same version of MS Word on my other machine with Windows Server 2019, but shows this strange behavior under Windows 11
I have a similar issue with my offline version of Word on a Windows 10 machine.
I have a highly structured document where every heading is followed by a table, and there are a lot of headings, which means that I now have a lot of orphaned headings at the bottom of pages. Keep with next is activated for all heading styles.
I have not worked on the document for a few weeks, but at the beginning of March everything was still OK, that is, keep with next would prevent page breaks between a heading and a table (no empty lines in between).
In the online version of Word, keep with next still seems to work, but I cannot store the file in OneDrive.
Does anyone have a solution for this?
Version information:
Office 365, 14931 20132
Stefan_Blom : This is a sample document with a similar structure than the original: https://parson01-my.sharepoint.com/:w:/g/personal/marion_knebel_parson-europe_com/ERVdrY6Ao6xJvzHCtnfy77oBizRq1eI3ikAn7EKgcHJDug?e=vdRadU
We also tried to open the original document on a different team members machine and there it works as normal. Her version is more advanced than mine, therefore I hope the problem is gone after the next Office update.
