VBA & Macro Problems

How to Fix VBA Error 400 in Excel Isoplot Add-in

Maira Mehtab Sep 27, 2026 868 views

Question details

The user is experiencing a Microsoft Visual Basic for Applications Error 400 when attempting to use plotting icons in the older Isoplot geochronology add-in within a subscription-based version of Excel.

Product: Microsoft Excel
Device & OS: not provided
Scenario: Clicking plotting icons in the Isoplot 4.15 add-in installed on a modern Microsoft 365 Excel subscription (version 2408).
Observed behavior: A VBA Error 400 dialog pops up, preventing the add-in from generating the requested geochronology plots.

Before you start

Verify your exact Excel version by navigating to File > Account, and ensure you have administrative privileges to manage COM or Excel Add-ins on your system.

Solution 1Recommended

Verify Add-in Compatibility with Microsoft 365

Older VBA add-ins like Isoplot 4.15 often lack compatibility with newer, subscription-based Excel updates, which can trigger Error 400.

Microsoft 365 receives continuous background updates that can alter backend architecture, often breaking compatibility with older 32-bit macros or static VBA add-ins.

Check exact Excel build number

Open Excel and click on 'File' in the top-left corner. Select 'Account' from the left menu and locate your exact version and build number under the 'About Excel' section (e.g., Version 2408).

Consult publisher documentation

Visit the official Isoplot publisher's website to confirm if Isoplot version 4.15 is officially supported on your specific Microsoft 365 build.

Download updated versions

If a newer version of the Isoplot add-in is available that supports modern 64-bit Excel, download and install it to replace your older files.

Developer Support Required: If no newer version exists, you may need to contact the add-in developer directly for a patch, as the Error 400 is tied to the macro code failing to execute in the updated Excel environment.

Solution 2

Unblock the Downloaded Add-in File

Windows often blocks macros in downloaded add-in files for security reasons, which can silently cause VBA Error 400 when the code attempts to run.

Free Microsoft Office alternative

Switch to WPS Office for a Stable Spreadsheet Experience

If outdated third-party add-ins and macros are causing continuous errors in your subscription-based software, consider WPS Office as a lightweight, free alternative. WPS Office provides excellent format compatibility, a familiar user interface, and built-in analysis tools, ensuring a seamless migration of your data without the heavy overhead.

1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install the software: Run the installer and follow the simple on-screen instructions to set up WPS Office on your device.
3. Open your files: Launch WPS Spreadsheet and open your existing data files directly to continue your analysis with comprehensive built-in charting tools.

Provides seamless format compatibility with Microsoft Excel files (.xlsx, .xls, .csv).Free and lightweight alternative to heavy, subscription-based spreadsheet programs.Features a familiar user interface, requiring zero learning curve for new users.Offers robust built-in data analysis and charting tools that do not rely on outdated external add-ins.

microsoft office alternative - wps office

Frequently Asked Questions

What does VBA Error 400 mean in Excel?

VBA Error 400 is a generic Visual Basic for Applications error indicating that a macro or add-in failed to execute properly. It is frequently caused by compatibility issues between the macro's code and the Excel version, incorrect permissions, or missing object references.

Why do older add-ins fail in Microsoft 365?

Microsoft 365 frequently receives background updates that introduce new security protocols or change the backend architecture. These updates can break compatibility with older VBA add-ins designed for older, static versions of Excel, like Excel 2013 or 2016.

Can I run 32-bit VBA add-ins on a 64-bit Excel version?

Often, you cannot without modifications. If the original VBA code uses Windows API declarations without the 'PtrSafe' attribute, a 32-bit add-in will trigger errors (including Error 400) in a 64-bit Excel environment. The add-in developer must update the code to support 64-bit systems.

Excel & Data Problems