Deep dive · 04
VBA: The Automation Heart of Office
It arrived quietly inside a spreadsheet in 1993. Thirty-three years later it is, by some distance, the most widely deployed dialect of BASIC in history.
01One Basic to rule the macros
Before VBA, automating Microsoft's applications meant learning a different dialect for each of them. Excel spoke XLM, a macro-sheet language of arcane function codes. Word spoke WordBasic. Access had Access Basic. Each was a dead end: skills did not transfer, code did not move, and none of them talked to each other. Visual Basic (the product line whose rise is traced in our history) had just demonstrated what a friendly Basic with a visual environment could do for application building. The obvious question followed: what could it do for application using?
The answer shipped in 1993 inside Excel 5.0, the first application to embed the new engine under the name Visual Basic for Applications. Instead of macro sheets, you got modules, a proper code editor, and an object model (Range, Worksheet, Workbook) that turned the application itself into a programmable object. Over the following years the engine spread through the suite: Project, then Access and PowerPoint, and finally Word in its 97 release, which retired WordBasic after more than a decade of service.
02The model that made it stick
Three design decisions explain VBA's longevity. First, it was hosted: the editor (the VBE, Visual Basic Editor), the debugger with its Immediate window, breakpoints and watches, and the Object Browser all lived inside the application, so the distance between "using Excel" and "programming Excel" was one keystroke (Alt+F11, a shortcut millions can still type from muscle memory). Second, it was recordable: the macro recorder translated your menu actions into Basic, giving every beginner a personalised, editable tutorial. Third, it was shared: once the engine lived everywhere, code written for one application could drive another through COM automation (Access could push data to Word, Excel could command Outlook) turning Office itself into a development platform.
The syntax was the classic Visual Basic of the era, close kin to VB6, Dim, For Each, On Error GoTo, with the host's object models layered on top. Canonical VBA patterns live in the code depot.
03The virus decade
Success had a shadow. A language embedded in documents, executed on open, distributed by email attachment, the nineties did not need to think hard about how to abuse that combination. Macro viruses became the era's signature malware, culminating in 1999 in Melissa, a Word macro worm that forwarded itself through Outlook address books and knocked major organisations offline. The industry's response reshaped VBA's world: Microsoft introduced macro security levels, digital-signing of projects, and ultimately the Trust Center, while enterprise gateways learned to strip macros from documents entirely.
The pendulum eventually swung the other way. In recent years Microsoft has tightened the screws further, blocking macros in files downloaded from the internet by default (a sensible policy that nevertheless lands hard on legitimate VBA users), who now coach colleagues through unblocking dance routines. The security story of VBA is really the story of an innocent 1993 design colliding with the internet's darker decade.
VBA and VBScript are siblings, not twins (VBA is compiled and hosted inside applications with full dev tooling); VBScript was an interpreted, lighter dialect for the web and admin scripting. The contrast is drawn in our VBScript retrospective.
04The 2026 situation: still beating
Microsoft has, at various moments, signalled enthusiasm for successors, Office Scripts and its JavaScript API, add-ins built on web technologies, and at each moment the installed base of VBA has quietly declined to move. The practical reality in 2026: VBA still ships in every desktop edition of Microsoft 365, remains the only automation layer that works everywhere Office works, and still runs the reporting pipelines, reconciliation scripts and data cleanup routines of a few hundred million spreadsheets. Its community (forums, Q&A archives, YouTube channels) remains one of the largest in programming; the map is in Where Classic VB Lives On.
The depot's verdict: VBA is no longer where Microsoft invests, but it is also not going anywhere, and the realistic strategy for most organisations is maintain-and-contain rather than rewrite-overnight (the same honest arithmetic we apply to VB6 migrations.
Excel did not just get a macro language in 1993. It got a constitution) one that analysts, auditors and engineers have been amending ever since.