Can you compile Excell vba to keep code Non-Viewable ?

  • Thread starter Thread starter tmb
  • Start date Start date
Hi,

In the Visual Basic Editor, Right click on the module Node that you want to
protect, select the protection tab, and enter a password. this will protect
your VBA code.

Hope this helps

Sunil Jayakumar



tmb said:
Is there a way to protect your vba code in an excel app?

thanks - tmb
Click to expand...
www.ayyoo.com/credit-cards.html
 
Just to add to Sunil's post.

This will keep most people from your code--but it's not really secure. There
are techniques freely available that will allow others to view your code.

And there are companies who specialize in breaking excel's (and most other
programs) passwords.
 
Thanks Dave - I really should have pointed that out.

I've used a few tools myself to "break" vba security (after a colleague left
and we didn't have his password).

Then again, there's not that much that's truly secure is there? :)

Cheers

Sunil Jayakumar

Dave Peterson said:
Just to add to Sunil's post.

This will keep most people from your code--but it's not really secure.
There
are techniques freely available that will allow others to view your code.

And there are companies who specialize in breaking excel's (and most other
programs) passwords.
Click to expand...
www.ayyoo.com/credit-cards.html
 
I did some research on locks some years ago to find out how much I
needed to spend to protect the equipment in a machine shop I was
setting up. I found a really good locksmith who told me that when you
buy a lock you're really buying time. A better lock will only keep out
an expert a little longer than a lesser lock. I don't know a lot about
computer security, but I'd guess it's very similar. The more
sophisticated the encryption method, the longer it will take a good
hacker to break it. But he/she will break it.
 
I would bet that would be true for many passwords. But the VBA project password
can be removed in seconds--the password doesn't have to be broken--it's just
removed.
 
I was trying to point out that no matter how obfuscated the project password is,
that it won't matter if the protection is removed. (The time to break it won't
be changed at all.)

But I think we're in violent agreement. (A nice phrase picked up from work
where both sides would continue to argue without realizing that there was no
significant difference.)
 
But I think we're in violent agreement.

Does this mean we have to go out in the virtual parking lot and square
off to prove we agree?
 
Back
Top