VBA Still Matters in 2026: When Macros Beat Low-Code for Everyday Business Automation

If your day-to-day work happens in Excel or Access, the best automation tool is often the one that works inside the files and processes you already use.

Despite the growth of low-code platforms, cloud automation and Python, Visual Basic for Applications (VBA) remains a practical and effective choice for many business workflows in 2026. It can automate repetitive tasks, validate data, generate reports and connect Microsoft Office applications without forcing users to adopt an entirely new system.

As a sole trader designing Excel and Access automation for UK organisations, I am often asked whether VBA is obsolete.

It is not.

A better question is: when is VBA still the right tool, and when should you choose Power Automate, Python, SQL or a bespoke system instead?

In this article, I look at where VBA continues to deliver value, the situations where other technologies are a better fit, and the practices that keep macro-driven solutions maintainable, secure and easy to hand over.

Is VBA still useful in 2026?

Yes — particularly when the workflow already lives in Microsoft Office.

VBA runs directly within applications such as Excel, Access, Word and Outlook. That makes it particularly useful when you need to automate a process while keeping the familiar interface your users already know.

A well-designed VBA solution can:

• Clean and transform data inside Excel.
• Validate inputs before errors enter a process.
• Refresh data and assemble management reports.
• Generate PDFs and scheduled report packs.
• Export data in consistent formats.
• Automate repetitive tasks across Excel, Access, Word and Outlook.
• Provide clear prompts and guided workflows for users.

Because the automation sits close to the underlying workbook or database, VBA can also respond directly to worksheet values, named ranges, buttons, forms and other interface elements.

For relatively contained Office-based processes, that can make VBA one of the quickest ways to move from a manual task to a reliable automated workflow.

VBA vs Power Automate vs Python: which should you choose?

There is no single best automation technology. The right choice depends on where the work happens, how users interact with it and how far the process needs to scale.

Choose VBA when:

The process already happens primarily in Excel or Access.

You need immediate validation or feedback while a user is working.

The automation depends on workbook, worksheet, form or control context — for example named ranges, selected records, form values or worksheet states.

You need precise control over the order in which tasks run.

The process may need to work offline or within a restricted network environment.

You want to improve an existing Office-based workflow without introducing additional services, connectors or deployment overhead.

Choose Power Automate when:

The main requirement is to coordinate activity between systems.

Typical examples include routing approvals, moving documents between platforms, responding to cloud-based events, updating SharePoint or Teams, and connecting Microsoft 365 services.

Power Automate is particularly effective as the glue between applications and services.

Choose Python when:

You need heavy data processing, advanced analytics, machine learning, complex API integrations or larger-scale ETL processes.

Python is extremely capable, but it does not automatically make it the best choice for a finance or operations team whose workflow revolves around clicking a button in an Excel workbook.

The technology should fit the process and its users — not the other way around.

Sometimes the best solution is a hybrid

VBA, Power Automate and other technologies do not have to compete.

A common approach is to use VBA for the interactive, in-workbook part of a process and Power Automate for activities that happen elsewhere.

For example:

1. A user runs a VBA routine in Excel.
2. The macro validates the data and highlights any problems.
3. Once the checks pass, it refreshes the report and generates a PDF pack.
4. A Power Automate flow archives the files in SharePoint, sends notifications or records an audit entry.

This keeps the responsive Excel experience users are familiar with while using cloud automation where it adds the most value.

Five situations where VBA is often the fastest route to value

1. Month-end and management reporting

A VBA routine can turn a long checklist into a controlled process.

For example, a macro might:

• Roll reporting periods forward.
• Refresh queries and connections.
• Update formulas or dynamic ranges.
• Run reasonableness and completeness checks.
• Highlight missing information.
• Generate a standard set of reports.
• Export the finished pack to PDF.

A process that previously relied on someone remembering 15 manual steps can instead become a repeatable routine with built-in checks.

2. Inventory and operational worksheets

Many businesses still run important operational processes in Excel.

VBA can add practical features such as barcode lookups, reorder warnings, guided data entry, stock checks and supplier-ready exports without requiring an entirely new application.

Where the workbook is already an established part of the process, improving it can be far quicker and less disruptive than replacing it.

3. Access data-entry systems

Microsoft Access remains useful for structured internal applications where forms, queries and reports are needed quickly.

VBA can enforce business rules directly on data-entry forms, including:

• Valid value ranges.
• Required fields.
• Status transitions.
• Cross-field validation.
• Duplicate checks.
• Conditional workflow rules.

Catching problems when a record is entered is usually much easier than cleaning them up later.

4. Word document generation

VBA can pull approved data from Excel or Access and use it to generate consistent Word documents.

This is useful for recurring reports, letters, certificates and other documents where manual copying and pasting creates unnecessary risk.

The result is faster document production with fewer transcription errors.

5. Outlook and email automation

VBA can also support controlled email processes.

For example, a routine might generate a report, create the appropriate PDF attachments, prepare a standard email and address it using an approved distribution list.

Depending on the organisation's security policies, it may also be possible to automate parts of the sending process.

As with any email automation, appropriate controls and logging are important.

When Excel or Access starts to outgrow VBA

VBA is useful, but it should not be stretched beyond its natural limits.

Warning signs that a process may need a different architecture include:

• Large numbers of simultaneous users.
• Increasingly complex permissions.
• Multiple teams editing the same data.
• Growing performance problems.
• A need for stronger audit trails.
• Large data volumes.
• Business-critical integrations with several external systems.

In these cases, the answer does not always have to be an immediate move away from Excel.

One practical option is to keep Excel as the reporting or analysis interface while moving the underlying data into a properly designed SQL database.

Similarly, an Access front end can sometimes be retained while its tables are migrated to SQL Server.

This allows users to keep a familiar interface while the database provides stronger performance, integrity and scalability.

Can VBA run scheduled tasks and email PDFs?

Yes, although the right approach depends on the environment and the organisation's IT policies.

Common options include:

Excel Application.OnTime

Application.OnTime can be used to schedule a VBA procedure while Excel and the relevant workbook remain open.

This can work well for recurring tasks during an active Excel session.

Windows Task Scheduler

Windows Task Scheduler can be used to launch a macro-enabled Excel workbook or Access database at a defined time.

A startup routine can then run the required process and close the application when complete.

Automated PDF generation

Excel's ExportAsFixedFormat method and Access report exports can be used to generate standardised PDF files.

These can then be attached to Outlook emails or passed into another distribution process.

For any unattended or semi-automated routine, I recommend building in proper logging so you can see:

• When the process ran.
• Whether it completed successfully.
• Which files were created.
• What data was processed.
• Any warnings or errors that occurred.

You should also check your organisation's IT and security requirements. Macro security, trusted locations, code signing and approved mail profiles may all need to be considered.

What about Microsoft Access and VBA in 2026?

Access remains a practical option for some internal business applications.

It can be particularly effective when you need to build structured forms, apply business rules at the point of entry and generate repeatable reports without the time and cost of developing a completely bespoke application.

VBA extends that capability by allowing more sophisticated validation, navigation and workflow automation.

For growing systems, Access can also provide a bridge to a more scalable architecture.

An Access front end can be linked to SQL Server tables, allowing users to retain familiar forms and reports while moving core data into a more robust database platform.

This staged approach can reduce the risk and disruption of a full replacement project.

Safe handover to a wider team

Handover should be part of the delivery process, not something assembled at the last minute.

A well-prepared handover should include:

• A versioned workbook, template or packaged Access front end
• An .accde build for current Access applications where appropriate
• An .mde build only for legacy .mdb applications
• A short operations guide
• A description of inputs, outputs and dependencies
• Recovery instructions
• A change log
• A documented update and release process
• Sample data
• A smoke-test checklist
• Ownership details for source files and service accounts

Passwords and credentials should be transferred through an approved secure channel and rotated where appropriate.

The aim is to ensure that the team can operate the solution independently, while still having a clear route for support or future enhancements.

Frequently asked questions

Is VBA obsolete in 2026?

No. VBA is still useful for Office-based workflows that require precise control, quick user feedback and close integration with Excel, Access, Word or Outlook.

It is not the right technology for every problem, but neither is Power Automate, Python or bespoke software.

When should I choose VBA over Power Automate?

Choose VBA when the process happens primarily inside an Office application and needs direct interaction with workbook data, Access forms or the user interface.

Choose Power Automate when the main requirement is to connect cloud services, respond to events or orchestrate a process across multiple systems.

When should I choose Python instead of VBA?

Python is generally a better fit for large-scale data processing, advanced analytics, machine learning, complex API integrations and more substantial ETL pipelines.

For a contained Excel or Access workflow used directly by business users, VBA may still be simpler to deploy and easier to integrate into the existing process.

Can VBA schedule tasks and send PDFs by email?

Yes. Depending on the environment, VBA solutions can use techniques such as Application.OnTime, Windows Task Scheduler, PDF export and Outlook automation.

Any automated process should include appropriate logging, error handling and security controls.

How do I keep VBA macros maintainable?

Keep code modular, use consistent error handling, separate configuration from code, document the workflow and maintain a version history.

For important processes, add repeatable tests and a simple verification checklist.

What is the safest way to hand over a macro-driven workbook?

Provide a versioned production file, operating instructions, a change log, sample test data and a verification process.

The client should also receive ownership of the relevant source files and any credentials required to operate the solution.

The bottom line: VBA still has a place

VBA still earns its place in 2026.

When a business process already lives in Excel or Access, VBA can provide fast, precise automation without forcing users to abandon familiar tools.

It is particularly effective for:

• Data preparation and validation.
• Repetitive reporting.
• PDF and file generation.
• Controlled exports.
• Office-to-Office automation.
• Guided Excel and Access workflows.

Power Automate is often the better choice for coordinating processes across cloud services. Python is stronger for advanced data processing and analytics. SQL databases and bespoke software become increasingly appropriate as requirements for scale, governance and multi-user access grow.

The important thing is not to choose a technology because it is fashionable.

Choose the simplest tool that solves the problem reliably, can be maintained properly and fits the way people actually work.

If you would like an independent view of where VBA fits into your current setup, Contact us to book a free initial consultation.

I can review an existing workbook, Access database or manual process, identify practical quick wins and outline whether VBA, Power Automate, SQL or another approach is the most sensible next step.