The Problem (Q-score 5, ranked #86th of 95 in the VBA Core archive)
The scenario as originally posted in 2012
I’m writing a .Net application that utilises Excel. Any version of Excel from ’97 or later is acceptable, but I don’t know which version any particular client will have. Installing the Microsoft Office PIAs through a bootstrapper is no problem.
Which version of the PIA should I include in the installation package? Do I need every PIA version, or will one PIA version cover all required Excel versions?
Why community consensus is tight on this one
Across 95 VBA Core entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — niche answer (below median) (+6)
Advisory answer — community consensus with reference links
Note: the verified answer below is a reference / advisory response rather than a copy-ready snippet.
Using the earliest PIA version should work, albeit unofficially – see MS Office PIAs "backward compatibility". Using a later version may or may not work, and is not recommended.
When to Use It — vintage (14+ years old, pre-2013)
Ranked #86th in its category — specialized fit
This pattern sits in the 95% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the VBA Core archive for a higher-consensus alternative.
What changed between 2012 and 2026
The answer is 14 years old. The VBA Core 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.