Worried that someone will reverse engineer your VBA code?...
Make it less worthwhile for them by removing redundant compiler junk from MDE and ADE files using this easy to use utility.
Why normal MDE files created by Microsoft® Access are vulnerable...
Normal MDE files created by Microsoft® Access contain extra information that we like to call "compiler junk" - this is redundant information about variable names, data types, constants, UDTs etc that are no longer needed in a fully compiled MDE file.
However, this "compiler junk" makes it much easier to decompile and reverse-engineer the VBA code in an MDE file to a standard that is very close to the original VBA source code (including, for example, all variable names).
In fact, for those that can prove ownership of their MDE files, we at EverythingAccess.com offer a service for reverse-engineering them including all VBA code. You must be able to prove lawful ownership beyond any doubt for our service - but that is not to say that another company (or utility) won't offer a non-validated conversion service in the future.
FAQ: But I thought that the VBA source code in my MDE file had been stripped out?
Yes, you're quite correct. However, the source code can be re-built with very high accuracy by using the combination of the compiled code and the "compiler junk" which is left behind by Access when creating the MDE file.
The solution - MDE Source Code Protector
If you want to better protect your VBA code, then the solution is to remove the extra "compiler junk" from the MDE file completely which makes it much harder and much less desirable to decompile/reverse-engineer the source code.
Removing the "compiler junk" does not prevent decompiling/reverse-engineering the VBA code, but it does make it that much harder and the result would be source code that does not look anything like the original source code (and therefore much less understandable). Example reverse engineered source code before and after protection
FAQ: Doesn't the /decompile switch do this?
No. The Access /decompile switch removes the compiled VBA code from an MDB file, ready for re-compiling. As soon as the VBA code is compiled again, the compiler junk exists again. Since all MDE files have to be compiled, the compiler junk is always present and makes it very easy to decompile (unless you use our MDE Source Code Protector software).
Key features:
- Easy to use utility for removing "compiler junk" that is left behind in an MDE file created by Microsoft Access
- After using this utility, reverse engineering (or decompiling) the VBA source code produces far less desirable results.
- Use this utility to view exactly what is being exposed in your MDE file - you may be surprised at the results! (Constant values are hidden to prevent malicious use of this software)
- After using this utility, the VBA source code is fully stripped from the MDE file - equivalent of a standalone VB6 application
- Supports Access 97, 2000, 2002 (XP) and 2003
- Also supports ADE files (compiled Access Project files)
View Cart