Hi, you all know the password protection for VBA projects is broken by so
many programs, so our codes are totally open.
I have been advised to create COM applications externalising code from the
modules but I don't want to.
Is there any possibility to completely block the add-in so not even me can
access it once the workbook has been saved as xla?.

Thanks!

nope.

Those programs that can break the password, er, can break the password.

econcult wrote:

Hi, you all know the password protection for VBA projects is broken by so
many programs, so our codes are totally open.
I have been advised to create COM applications externalising code from the
modules but I don't want to.
Is there any possibility to completely block the add-in so not even me can
access it once the workbook has been saved as xla?.

Thanks!

--

Dave Peterson

I don't mean 'shield the project by means of a password' but 'block the
project so not even me can open it again'.


"Dave Peterson" wrote:

nope.

Those programs that can break the password, er, can break the password.

econcult wrote:

Hi, you all know the password protection for VBA projects is broken by so
many programs, so our codes are totally open.
I have been advised to create COM applications externalising code from the
modules but I don't want to.
Is there any possibility to completely block the add-in so not even me can
access it once the workbook has been saved as xla?.

Thanks!

--

Dave Peterson

Again, nope.

econcult wrote:

I don't mean 'shield the project by means of a password' but 'block the
project so not even me can open it again'.

"Dave Peterson" wrote:

nope.

Those programs that can break the password, er, can break the password.

econcult wrote:

Hi, you all know the password protection for VBA projects is broken by so
many programs, so our codes are totally open.
I have been advised to create COM applications externalising code from the
modules but I don't want to.
Is there any possibility to completely block the add-in so not even me can
access it once the workbook has been saved as xla?.

Thanks!

--

Dave Peterson


--

Dave Peterson

What you are asking is equivalent to saying, "can something be encrypted so
it can't be decrypted?" The answer is no. I could give a long explanation,
but one point should serve to illustrate: If it is impossible to decode, how
can Excel use your project? And if Excel can decode it, couldn't someone
with the right tools and knowledge follow the same steps Excel is following?
The only way encoding makes sense is with strong password protection or some
equivalent key, but then it is the user's responsibility to keep the key
secure - and there is always a chance that with enough time and the right
tools, someone might learn how to duplicate that key. The best anyone can do
is to try to make it so difficult and time consuming to break the code that
it is not worth the thief's effort. But it would be irresponsible to trust
in any kind of encryption to provide "unbreakable" security. And, in a
theoretical sense, if it was unbreakable it would also be unusable.

"econcult" wrote:

Hi, you all know the password protection for VBA projects is broken by so
many programs, so our codes are totally open.
I have been advised to create COM applications externalising code from the
modules but I don't want to.
Is there any possibility to completely block the add-in so not even me can
access it once the workbook has been saved as xla?.

Thanks!