Best way to protect VBA code?

[mcomp72]

Hey everyone. I'm getting close to being finished with a Macro-Enabled Excel workbook I've been working on for a while now. I plan to release it publicly, but do not want anyone to be able to see my VBA code. I know I can password protect it, but I've read that it's fairly easy for someone to still get into the VBA window to view it. I'm wondering what other techniques anyone has used to protect their code?

I've heard of something called Unviewable+, but haven't tried it yet.
https://www.spreadsheet1.com/unviewable-vba-project-app-for-excel.html

Anyone have any experience with it? Or anything else that is similar that they'd recommend?

 

[Michael M]

Why not simply convert it to an Addin.
Have a look here at Method 3

https://www.wikihow.com/Protect-VBA-Code

 

[Kyle123]

Unviewable+ is trivial to circumvent, it’s as easy as just password protecting it.

Honestly, without rewriting it in another language, compiling it and referencing as an addin, you’d be better off just sticking a standard password on and calling it a day.

People pay for support and changes if that’s what you’re concerned about, they aren’t interested in the source code

 

[Unicam]

Unviewable+ is trivial to circumvent, it’s as easy as just password protecting it.

Honestly, without rewriting it in another language, compiling it and referencing as an addin, you’d be better off just sticking a standard password on and calling it a day.

People pay for support and changes if that’s what you’re concerned about, they aren’t interested in the source code

I've been using Unviewable+ at work and it doesn't show code but only an error message when you try to access said code. How would someone circumvent it? With a hex editor or something? I'd really love to know this.

 

[Fluff]

Please do not ask questions regarding the breaking of security, as it is against board policy.

 

[Joe4]

How would someone circumvent it? With a hex editor or something? I'd really love to know this.

As Fluff said, posting those details would violate rule 6 here: Message Board Rules
So please do not post those details here.

 

[Unicam]

As Fluff said, posting those details would violate rule 6 here: Message Board Rules
So please do not post those details here.

I understand that, but if there is a security risk to the VBA tools I've implemented, I need to figure out what that is because this is the first I've heard of it. Where can I find this out, any ideas?

 

[sandy666]

You can try

VBA Obfuscator

Protect a VBA code (Excel): obfuscation is the only effective solution to protect a VBA code against copying, modification...

www.excel-pratique.com

or any paid version

 

[Fluff]

Where can I find this out, any ideas?

Try searching the net. We cannot tell you how to break/bypass any form of security.

 

[Unicam]

By now I'm pretty sure I've looked everywhere. There is no mention of the security Unviewable+ provides to Excel files being circumvented. I suspect Kyle's remark is unfounded and not based on actual experience or documentation. I can highly recommend the application to any builder who wants to keep his/her code private. Just be careful you do it with a copy that you share with your users and not the actual file you work in, or you'll never be able to modify the code! Thankfully my employer provides a separate development environment as well as one for testing, but in the beginning I did make that mistake myself. Thank goodness for backups