Tables split or they start writing in 2 places when I'm writing one sentence.

Maureen Giannotti 0 Reputation points
2026-03-07T21:56:14.6033333+00:00

I'm having trouble with my tables when I insert them into my work documents. They split or they start writing in 2 places when I'm writing one sentence.

I'm an experienced user and have been creating documents and tables for years. I really need help for my work as a math curriculum writer.

Microsoft 365 and Office | Word | For home | Windows

1 answer

Sort by: Oldest
  1. AI answer

    2026-03-07T21:56:26.5633333+00:00

    Try these targeted checks and fixes in Word for Microsoft 365 on Windows.

    1. Stop tables from splitting across pages

    If rows are breaking in odd places or the table is splitting:

    1. Click anywhere in the table, then select the whole table (Table handle at the top-left or drag-select).
    2. Open the Paragraph dialog (for example, right-click → Paragraph).
    3. Go to the Line and Page Breaks tab.
    4. For each row except the last one, ensure Keep with next is applied; for the last row, it should be off. If you selected many rows and see a filled (gray) box instead of a clear check mark, click twice to turn the option fully on or off as needed. Word does not always show the true state when multiple rows are selected.
    5. Also review Widow/Orphan control and other pagination options; if all are checked when you select the whole table, clear them and reapply only what is needed.

    This ensures the table stays together on a page as far as possible and prevents unexpected splitting.

    1. Fix tables that seem to “write in two places” or resize/flicker

    If typing in a table causes text to appear oddly, the cursor to blink strangely, or the table to resize or jump (especially in headers/footers or multi‑section documents):

    1. Check whether the table is in a header or footer and the document has multiple sections with different margins or orientations and Same as Previous turned on. That combination can cause flicker and continuous resizing.
    2. Right‑click the table → Table Properties → Table tab:
      • Turn off Automatically resize to fit contents if it is enabled.
    3. Still in Table Properties, check column widths:
      • If the table width is set as a percentage and each column also uses percentage widths, make sure the sum of the column percentages does not exceed the table’s total percentage.

    These changes prevent Word from constantly recalculating the table layout while typing.

    1. Check for known table-layout bugs and updates

    Recent builds have had table-layout issues (for example, layouts changing unexpectedly after an update). Make sure Office is fully updated to the latest build, because several table issues are marked as fixed in newer versions.

    If the behavior started right after a specific update and persists after updating to the latest build, use Help → Feedback → Report a problem in Word to send a sample description and document (if possible) to the Word team.

    1. If the table is in a header/footer and the cursor blinks abnormally

    If the symptoms match: abnormal cursor blinking, header/footer table flickering, or continuous resizing in a multi‑page, multi‑section document with different margins/orientations and Same as Previous headers/footers:

    • Avoid using auto‑resizing or percentage‑based widths that overfill the table, as described above.
    • Consider simplifying the header/footer table (fewer columns, fixed widths) or moving complex layout elements into the main body instead of the header/footer.

    If these steps do not resolve the issue, gather a small sample document that reproduces the behavior and post it (with any confidential content removed) to the Word community forums for targeted analysis.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.