How to protect VBA code from un authorised access
Hi Team,
I am facing a huge problem in terms of the vba.code protection from unauthorised access. Even if the same is passward protected it seems that you easily break vba passward lock.
Can some please suggest a better solution to protect my codes from being accessed without my permission. I design and send developed tools to different teams to make their work simple.
Sandesh1983 Jadhav
I am facing a huge problem in terms of the vba.code protection from unauthorised access. Even if the same is passward protected it seems that you easily break vba passward lock.
Can some please suggest a better solution to protect my codes from being accessed without my permission. I design and send developed tools to different teams to make their work simple.
Sandesh1983 Jadhav
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You could use VB6 (or VB.Net) to create an executable that creates and/or updates an Excel spreadsheet. Code in such an executable can not be decompiled.
@MartinLiss
I'm not sure what you are basing your assumption on, I have successfully decompiled .Net code.
I'm not sure what you are basing your assumption on, I have successfully decompiled .Net code.
Okay I guess I overstated and should have said that VB programs compiled to native code are not easily decompiled to human-readble form. Yes the hacker might be able to see what's going on but at least you're putting another obstacle in his path.
Note that there are 3rd-party programs that can be used to protect exe's from hacking.
Note that there are 3rd-party programs that can be used to protect exe's from hacking.
Note that there are 3rd-party programs that can be used to protect exe's from hacking.
And there are those that enable decompiling, such as those that I've used before.
A better question might be... Why are the persons you are distributing the tools to trying to crack the password protection in the first place?
If they do crack it and manage to update something... you still have the original code correct?
My point being here is that you could establish a guideline that let's people know that you will only be supporting the original code... and that if they choose to change it, that they are on their own from a support perspective.