XLS Padlock lets you not only lock the VBA project of your Excel workbooks (or prevent access to the VBA editor), but also compile your sensitive VBA code into working bytecode not accessible to final users. Your VBA macros are protected and cannot be studied/copied because the original VBA code does not exist anymore. The compiler is not a simple obfuscator: it completely turns VBA code into binary code and stores it securely in the application.
Other VBA protection can be easily defeated, even VBA obfuscation is not a real protection: discover XLS Padlock's VBA compiler as a better alternative.
With XLS Padlock, you can lock your VBA project securely: this feature doesn’t use password protection, it marks the VBA project as locked: it can’t be viewed, accessed or modified in VBE (Visual Basic Editor). If the end user tries to access a locked VBA project, the following error message is displayed (Project Locked – Project is unviewable):
Since the original Excel file cannot be recovered, Excel VBA password-cracking tools are useless. Moreover, this option is compatible with our VBA compiler, to increase the security of your VBA code.
This is an additional security measure that will automatically close the VBA editor if the end user tries to open it. So your VBA project remains inaccessible.
This option is compatible with VBA password protection and our VBA compiler.
XLS Padlock features an integrated VBA compiler: you can write Basic scripts and compile them into working bytecode not accessible to others.
Turning parts of your VBA macros into compiled code allows you to secure them: the original code does not exist anymore and it cannot be copied. Your VBA code is definitively protected, even without VBA password protection.
For instance, see this original code:
Once protected, it becomes:
As you can see, the original code in calculate() has been replaced by a call to XLS Padlock’s built-in function named PLEvalVBA. This function executes the compiled bytecode. There is no way for the final user to access the bytecode and, of course, the calculate() VBA function remains fully-functional (even in the original Excel workbook, before compilation).
The original VBA code of calculate() has been moved into the XLS Padlock VBA Editor and compiled there, as you can see below:
Our VBA compiler is not a simple obfuscator: it completely turns your VBA code into binary code and stores it securely in the application.
You can see how this works thanks to our online video.