Ultimate protection or is it?

[ndendrinos]

I was told just now by Smitty that:

Programmatic protection isn't supported in Shared workbooks.

Tested his saying and true enough he is right.
Once the file is shared you cannot see the VBA editor as it request a non existent password.
What I’m interested is this.
If I set up a "shared" file with macros and email it to someone wouldn’t that make it secure as far as the recipient seeing the codes and editing them?
We’ve been told that Excel is not a secure environment but then again how can a shared WB be cracked iin such a scenario?
If “shared” means that the file has to be on a common drive will the file work on another
computer NOT on the same drive? (hope I explain this well)
I have no way of testing the validity of what I’m saying but maybe someone can comment?
Thanks

 

[bjurney]

If the user unsahres the workbook, they will then be able to see the code. You can set up a password for your VBA project under tools> VBAProject Properties> Protection and then enter your password.

 

[MrKowz]

We’ve been told that Excel is not a secure environment but then again how can a shared WB be cracked iin such a scenario?

There are free, very easy to get, tools out there that can strip any password protection on a workbook. Password protection in Excel is basically there to keep the normal user honest.

Discussion about where to get these tools is strictly against board policy, but know that they do exist.

 

[ndendrinos]

not sure I understand you bjurney but I'm interested ... how can you "unshare" a WB?
MrKowz: so these tools can strip a non existent password? never thought they could.
So converting the file to an exe is still the solution then