Word VBA - Eliminate Floating Object Tables

Q: Which Word VBA pattern ranks just above this one at #7?

The pattern one rank above is “SaveAs vs SaveAs2 in the Microsoft Office Word object model”. If your use case overlaps, compare both before committing.

The Problem (Q-score 13, ranked #8th of 32 in the Word VBA archive)

The scenario as originally posted in 2015

I have a ton of Word documents with somewhat “corrupted” tables. I’ve been able to automate most of the repair process, but one issue is still beyond me.

Many of the tables are floating objects – when I show the hidden formatting marks, I see an anchor by the table. I can’t leave the documents like this, I need to make everything inline.

I do have a segment of code that “fixes” this, but I don’t think it is a good solution. By changing the text wrapping from “None” (the default – what I want it to be) to “Around” and back to “None”, this gets fixed. The code is,

Selection.Tables(1).Rows.WrapAroundText = True
Selection.Tables(1).Rows.WrapAroundText = False

I’m sure there is a better way to do this. Does anyone know of something that will work? Thanks!

Why community consensus is tight on this one

Across 32 Word VBA entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.

The Verified Solution — solid answer (above median) (+7)

6-line Word VBA pattern (copy-ready)

I have no idea why flapping the WrapAroundText flag solves your problem, VBA has alot of quirks like that.

Automating this method to all of the tables in the document is fairly simple:

Dim i as Integer
For i=1 to Len(ActiveDocument.Tables)
  ActiveDocument.Tables(i).Rows.WrapAroundText = True
  ActiveDocument.Tables(i).Rows.WrapAroundText = False
Next i

When to Use It — classic (2013–2016)

A top-10 Word VBA pattern — why it still holds up

Ranks #8th of 32 in the Word VBA archive. The only pattern ranked immediately above it is “SaveAs vs SaveAs2 in the Microsoft Office Word object model” — compare both if you’re choosing between approaches.

What changed between 2015 and 2026

The answer is 11 years old. The Word VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Is this above-median answer still worth copying?
expand_more

Answer score +7 vs the Word VBA archive median ~4; this entry is solid. The score plus 13 supporting upvotes on the question itself (+13) means the asker and 6 subsequent voters all validated the approach.

Does the 6-line snippet run as-is in Office 2026?
expand_more

Yes. The 6-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

Published around 2015 — what’s changed since?
expand_more

Published 2015, which is 11 year(s) before today’s Office 2026 build. The Word VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Word VBA pattern ranks just above this one at #7?
expand_more

The pattern one rank above is “SaveAs vs SaveAs2 in the Microsoft Office Word object model”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 13, Answer-score 7, original post 2015, ranked #8th of 32 in the Word VBA archive. Last regenerated April 14, 2026.

Word VBA – Eliminate Floating Object Tables