VBA itself is a 32-bit technology. DoneEx compiles to 32-bit DLLs. On 64-bit Excel, you must run in compatibility mode or use the 32-bit version of Office. This is a Microsoft limitation, not a DoneEx flaw.
| Pros | Cons | | :--- | :--- | | High Security: Source code is removed, offering genuine IP protection. | Dependency: The Excel file requires the accompanying DLL file to function. | | Licensing: Built-in tools to sell your Excel apps commercially. | Compatibility Updates: If Microsoft updates Excel significantly, compiled DLLs may require re-compilation or updates from DoneEx. | | Performance: Compiled binary code can sometimes run faster than interpreted VBA. | Debugging: Once compiled, debugging errors is more difficult as you cannot step through the code in the Excel VBA editor. | | Ease of Use: Generally easier than migrating an entire project to VB.NET or C#. | Cost: It is a paid commercial tool (though a trial is usually available). | DoneEx VbaCompiler for Excel
Once compiled, you cannot step through code with the VBA debugger. You must debug fully before compiling. Use extensive logging (write to a text file) if runtime errors occur after compilation. VBA itself is a 32-bit technology
It isn't perfect. Because the EXE acts as a wrapper around Excel, Unhandled Errors can crash the entire application rather than just breaking into debug mode. You need to have robust On Error Resume Next and error logging in place before compiling. Once compiled, you cannot step through code with
Also, the interface looks a bit "Windows 98," but the compiler was last updated in late 2025 for Office 365 compatibility, so it works perfectly on modern systems.
Excel is the standard for business modeling, but it suffers from a major security flaw: the VBA project. If you email an Excel file containing a proprietary pricing model or a complex simulation, anyone with basic technical knowledge can extract the logic.
DoneEx VbaCompiler solves: