The Problem (Q-score 5, ranked #19th of 32 in the Word VBA archive)
The scenario as originally posted in 2009
I am using Word and OpenXml to provide mail merge functionality in a C# ASP.NET web application:
1) A document is uploaded with a number of pre-defined strings for substitution.
2) Using the OpenXML SDK 2.0 I open the Word document, get the mainDocumentPart as a string and perform the substitution using Regex.
3) I then create a new document using OpenXML, add a new mainDocumentPart and insert the string resulting from the substitution into this mainDocumentPart.
However, all formatting/styles etc. are lost in the new document.
I’m guessing I can copy and add the Style, Definitions, Comment parts etc.. individually to mimic the orginal document.
However is there a method using Open XML to duplicate a document allowing me to perform the substitutions on the new copy?
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) (+8)
11-line Word VBA pattern (copy-ready)
This piece of code should copy all parts from an existing document to a new one.
using (var mainDoc = WordprocessingDocument.Open(@"c:sourcedoc.docx", false))
using (var resultDoc = WordprocessingDocument.Create(@"c:newdoc.docx",
WordprocessingDocumentType.Document))
{
// copy parts from source document to new document
foreach (var part in mainDoc.Parts)
resultDoc.AddPart(part.OpenXmlPart, part.RelationshipId);
// perform replacements in resultDoc.MainDocumentPart
// ...
}
When to Use It — vintage (14+ years old, pre-2013)
Ranked #19th in its category — specialized fit
This pattern sits in the 58% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Word VBA archive for a higher-consensus alternative.
What changed between 2009 and 2026
The answer is 17 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.