Skip to content

VBA Compilation

VBA Padlock’s core feature is its ability to compile VBA source code into native, protected DLLs.

Instead of leaving your intellectual property exposed in the insecure VBA editor, your logic is transformed into encrypted bytecode and moved into external library files. The Office document itself only contains a lightweight VBA Bridge module that acts as a secure connector.

VBA Compilation Overview

How it Works

Section titled “How it Works”

The pipeline starts from the VBA you already have: no rewriting, no copy-pasting.

Open your macro-enabled Office file. VBA Padlock extracts its VBA modules through a read-only COM session (macros stay disabled) and runs the compile gate: a per-procedure analysis deciding what can move into the DLL and what must stay in the document. The Protection Review shows every verdict with its reason.

Developer Tip: Because the extracted scripts are stored as plain text files, you can use AI Coding Agents (like Claude Code, Gemini, OpenAI Codex or Cursor) to refactor code, fix compatibility issues, or write entirely new protected modules.

Output Structure

Section titled “Output Structure”

When you produce, VBA Padlock writes the protected copy and a bin/ directory containing the files necessary for your application to run.

Distribution Package

  • MyWorkbook_protected.xlsm ← Protected Office file (wrappers + VBA Bridge)
  • Directorybin/ ← Distribution folder (required)
    • MyWorkbookrun32.dll ← 32-bit Secure Runtime
    • MyWorkbookrun64.dll ← 64-bit Secure Runtime
    • MyWorkbook.dll ← Your compiled logic (Satellite DLL)
ComponentResponsibilityProtection
Runtime DLLsInterface between Office and your code.Authenticode Signed by G.D.G. Software.
Satellite DLLStores your encrypted VBA bytecode.Cryptographic Integrity Verification.
Office FileUI and public entry points.VBA Project Password Protected.

Capabilities & Integration

Section titled “Capabilities & Integration”

Accessing the Office Environment

Section titled “Accessing the Office Environment”

Compiled scripts are not “disconnected” from your workbook. They have full, high-speed access to the host application.

  • Full Object Model: Use Application.ActiveWorkbook / ActiveSheet (Excel), Application.ActiveDocument (Word), Application.ActivePresentation (PowerPoint), or Application.CurrentDb (Access). Unqualified host globals are qualified automatically during conversion.
  • COM Support: Use CreateObject for FileSystemObject, ADODB, or custom libraries.
  • Built-in API: Access over 80 specialized functions for licensing and security.

Code Example: What Produce Generates

Section titled “Code Example: What Produce Generates”

After production, each protected procedure is replaced in the document by a delegating wrapper with the same name and signature, so every button, event, and formula that called it keeps working:

' --- COMPILED SIDE (moved into the DLL) ---
Public Function CalculateTax(Amount)
    ' This code is invisible to the user and survives reverse-engineering
    CalculateTax = Amount * 0.20
End Function
' --- OFFICE VBA SIDE (the generated wrapper left in the document) ---
Public Function CalculateTax(Amount)
    CalculateTax = VBAPL_Execute("Financials|CalculateTax", Amount)
End Function

Integration with Microsoft Office

Section titled “Integration with Microsoft Office”

A common misconception is that compiled code is “isolated” from your document. On the contrary, your protected scripts have full, native access to the host application.

Support per Application

Section titled “Support per Application”
Host ApplicationGateway ObjectTypical Usage
Microsoft ExcelApplication.ActiveWorkbookRead/Write cells, format ranges, protect sheets.
Microsoft WordApplication.ActiveDocumentGenerate reports, replace bookmarks, manage sections.
Microsoft AccessApplication.CurrentDbExecute SQL queries, open recordsets, manage data.
Microsoft PowerPointApplication.ActivePresentationCreate slides, automate animations, export to PDF.

Pro Tip: Moving your heavy data processing into the compiled DLL is not only more secure, it is often faster because it bypasses the overhead of the standard VBA interpreter for complex logic.

Security & Reliability

Section titled “Security & Reliability”
  • Native Performance: Bytecode is executed by a custom-built virtual machine optimized for VBA logic.
  • Anti-Tamper: The Satellite DLL is bound to the Runtime DLLs. Modify one, and the application will refuse to load.
  • AV Friendly: Our runtime DLLs are digitally signed, ensuring high trust with antivirus software and Windows SmartScreen.

Next Steps

Section titled “Next Steps”