Use DoneEx if:
Avoid if:
It takes your VBA code and converts it into native machine code (C++ syntax protection). The result is a standalone .EXE file that runs without Excel even being visible (or with minimal Excel interaction). DoneEx VbaCompiler for Excel
Here is the technical breakdown of what happens to your code: Use DoneEx if:
| Feature | Standard Excel (.xlsm) | DoneEx Compiled (.exe) | | :--- | :--- | :--- | | Source Code | Stored as plain text (hidden by weak password) | Removed entirely | | Recovery Tools | Easily cracked by free Hex editors | Cannot be restored to VBA | | Runtime | Inside Excel process | Standalone application | Avoid if:
A London-based risk firm built a Monte Carlo simulation in VBA. Clients demanded the tool, but sharing the .xlsm meant exposing their proprietary probability models. After using DoneEx, they distributed a compiled version. A former client later hired a developer to reverse-engineer the DLL—after two weeks of failed attempts, they gave up. The firm’s IP remained intact.
The Scenario: A logistics company created a routing algorithm in VBA. They sold the tool to 10 trucking firms. The Result: Within 6 months, 3 firms had cracked the password and modified the tool to remove the licensing fee. The Fix with DoneEx: The developer re-compiled the logic into an EXE. The trucking firms received a black box: data goes in, route comes out. Zero access to the logic. Revenue protection achieved.