The Problem (Q-score 9, ranked #7th of 32 in the Word VBA archive)
The scenario as originally posted in 2010
It looks like SaveAs has gone away in Office 2010 in favor of SaveAs2. What is going on here? Are there any important differences between the two? My fix has been to check for SaveAs2 first, and then fall back to SaveAs. Is this reasonable?
Why community consensus is tight on this one
Across 32 Word VBA entries in the archive, the accepted answer here holds strong answer (top 25 %%) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — strong answer (top 25 %%) (+11)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Word VBA entries ranked in the top 10 of the same archive.
It hasn’t gone away, you’ve just got another way to save the document. Save2() takes an extra argument, CompatibilityMode. If you don’t care about the compatibility mode then just keep using Save(). If you do then check Application.Version to verify that you can call Save2() without getting an exception.
When to Use It — vintage (14+ years old, pre-2013)
A top-10 Word VBA pattern — why it still holds up
Ranks #7th of 32 in the Word VBA archive. The only pattern ranked immediately above it is “programatically convert word docx to doc without using ole automation” — compare both if you’re choosing between approaches.
What changed between 2010 and 2026
The answer is 16 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.