How to protect VBA code and VBA project
To provide the most strong and reliable VBA code copy protection, the DoneEx XCell Compiler
uses 2 different approaches which are combined into one solution when you select all options of ‘VBA Protection’.
Blocking access to VBA project and VBA code.
Option ‘Unviewable VBA code’ blocks access to the VBA code, makes VBA project unviewable and disables VBA debug mode.
After applying this option, VBA Project and VBA code will be unviewable and unavailable in compiled application.
Only this message will see anybody who tries to see your VBA code. Any attempt to trace your VBA code will fail because VBA debug mode will be disabled.
VBA code modification.
Two options, the ‘Code obfuscation’and ‘Literals removing’, modify the VBA code in a way that remains VBA code workable but becomes crabbed and incomprehensible.
After applying ‘Literals removing’ option, the modified VBA code becomes tied to the XCell Compiler run-time library and will be workable in compiled application only.
After applying all 3 options simultaneously you will get the strongest VBA code copy protection which has the following advantages:
- The VBA code is unviewable and inaccessible from Excel VBA project.
- The VBA debug mode is disabled, so it is impossible to trace the VBA code.
- All comments and empty lines are removed from the VBA code.
- The VBA code with removed literals will not work outside of compiled application.
- The VBA code is modified so it is incomprehensible and unrecoverable.
Below you may see example of code transformation after applying both code modification options.
Original VBA code:
After applying both code modification options, ‘Literals removing’ and ‘Code obfuscation’, the VBA code is: