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.
Write your sensitive VBA logic directly within the VBA Padlock Studio editor. You can use standard VBA syntax and access the full Office Object Model.
Developer Tip: Because your scripts are stored as plain text files, you can use AI Coding Agents (like Claude Code, Gemini, OpenAI Codex or Cursor) to help you refactor code, fix compatibility issues, or even write entirely new protected modules.
Press F5 in the Studio.
VBA Padlock translates your source code into a unique, encrypted bytecode.
A project-specific Satellite DLL is generated, containing this secure code.
VBA Padlock automatically injects a VBA Bridge module into your Excel, Word, or PowerPoint file. This module contains simple “wrapper” functions that you call from your UI (buttons, events).
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).
COM Support: Use CreateObject for FileSystemObject, ADODB, or custom libraries.
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.
Execute SQL queries, open recordsets, manage data.
Microsoft PowerPoint
Application.ActivePresentation
Create 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.