VbaCompiler

  • VBA Compiler
    • Features by licenses
    • How to compile
    • Compiler options
    • Backend C Compiler
    • Excel VBA copy protection
    • Create trial / demo version
    • Protect Excel workbook template
    • Runtime API Functions
    • Custom Run-Time Messages
    • VBA command line compilation
    • Compile Time Troubleshooting
    • Workbook Run-Time Troubleshooting
    • Distribute Workbook
    • EULA
    • Privacy Policy
  • Best way to protect VBA code
  • VBA Speed Up
    • VBA Benchmarks
    • Optimize VBA code
  • Frequent Questions
  • Download
  • Order
  • Contact us

How to Distribute a Workbook

If you plan to monetize your Excel workbook or add-in, it is essential to protect your intellectual property before you distribute your workbook. Sharing an unprotected version exposes your VBA code to potential copying, viewing, modifying, or piracy, which could result in unauthorized use or redistribution of your product. Implementing robust copy protection measures ensures that your workbook can only be used by the customers that you authorize.

It is important to understand, however, that copy protection does not completely prevent the physical copying of files from one computer to another. Instead, it restricts access and functionality so that your workbook or add-in operates only on the computers that have been explicitly authorized by you.

 

Protecting VBA Code with VbaCompiler for Excel

The VbaCompiler for Excel is a powerful tool designed to protect your VBA code from being viewed, copied, or modified. It effectively serves as a copy protection and VBA code security solution for Excel workbooks and add-ins. When you compile your project using VbaCompiler for Excel, the tool produces one or more DLL (Dynamic Link Library) files containing your compiled VBA code, along with a workbook file that no longer contains the original VBA source code.

Depending on your configuration, the output may include:

  • One DLL file (for either 32-bit or 64-bit Excel)
  • Two DLL files (one for each architecture)

The workbook retains a minimal amount of connective VBA code that simply invokes the compiled functions from the DLL(s).

Because this process produces multiple files — typically a workbook and one or two DLLs — distributing them together to customers can sometimes create logistical challenges. The following sections describe several practical methods for distributing your compiled Excel solutions securely and conveniently.

Available Workbook Distribution Methods

 

Workbook + DLL File(s)

 

This is the most straightforward way to distribute a compiled workbook.
After compilation, you will have two or three files:

  • The compiled Excel workbook (XLSM, XLSB, XLS) or Excel add-in (XLA, XLAM)
  • One or two DLL files (for 32-bit and/or 64-bit Excel)

Distribution Steps:

  1. Compress all the output files (the workbook and DLL(s)) into a single ZIP archive.
  2. Send the ZIP file to your customers via email or make it available for download.
  3. Instruct your customers to extract all files into the same local folder on their hard drive before opening the workbook.

Important:
If a customer wants to move the compiled workbook to another location, they must copy all associated files together — the workbook and the DLL(s) — to ensure the program functions correctly.

 

Single Workbook File ( with Embedded DLL)

VbaCompiler for Excel can also embed the compiled DLL(s) directly into the workbook, producing a single, self-contained Excel file. In this case the workbook should be compiled with “Single file result (Embedded DLL)” option on.

Single File Result option is selected to use one file workbook distribution

This is the simplest and most user-friendly distribution method, as your customer only needs to handle one file. After receiving the workbook, the customer can copy it to their local hard drive and begin using it immediately.

If they wish to move the file later, they only need to copy the single workbook file, without worrying about separate DLL files.

 

Distribute Workbook Using Single Executable (EXE) File Using XCell Compiler

For an even higher level of protection and convenience, you can combine the VbaCompiler output (workbook + DLL) using the XCell Compiler. This process compiles everything into a single EXE file, which encapsulates both the workbook and the compiled DLL(s).

The resulting executable is easy to distribute and run — users simply execute the EXE file without needing to manage multiple components. This method also provides enhanced security, as the embedded DLLs are inaccessible to end users.

 

Distribute Workbook as Installer Package Using DoneEx Installer Maker

Another convenient option is to create a professional installation package using DoneEx Installer Maker, a free tool from the DoneEx.

This method bundles all necessary components (workbook and DLL files) into a single installation EXE. When users run the installer, it automatically places all required files in the appropriate folder on their system.

This approach provides:

  • A clean, user-friendly installation process
  • Automatic folder setup and file placement
  • Easier updates and version management

 

Apply Digital Signature for EXE or DLL files Before You Distribute Your Workbook

We highly recommend to apply digital signature to created EXE or DLL files to reduce possible antivirus false positive detection.

 

Summary

Protecting your Excel workbook or add-in before distribution is critical to safeguard your intellectual property and maintain control over your software. The VbaCompiler for Excel and associated tools provide several flexible options for distributing compiled workbooks, ranging from simple ZIP archives to single-file executables and professional installation packages.

Choosing the right distribution method depends on your desired level of protection, user convenience, and deployment complexity. Regardless of the method you choose, always ensure that your compiled workbook and its components remain properly protected and accessible only to authorized users.

 

  • VBA Compiler
    • Features by licenses
    • How to compile
    • Compiler options
    • Backend C Compiler
    • Excel VBA copy protection
    • Create trial / demo version
    • Protect Excel workbook template
    • Runtime API Functions
    • Custom Run-Time Messages
    • VBA command line compilation
    • Compile Time Troubleshooting
    • Workbook Run-Time Troubleshooting
    • Distribute Workbook
    • EULA
    • Privacy Policy
  • Best way to protect VBA code
  • VBA Speed Up
    • VBA Benchmarks
    • Optimize VBA code
  • Frequent Questions
  • Download
  • Order
  • Contact us
Copyright 2005-2025 © DoneEx LLC. All Rights Reserved.