Contact the former employee. She/he is legally obligated
to provide the password if the project was developed on
company time or was paid for by the company. I'd be
willing to have a crack at it if you can prove to me that
your company owns the code. However, I can't think of a
way to do that without describing the contents; e.g.
module names, Function names, a general description of a
procedure etc. You would presumably need the former
employee to do this - so why bother, just get the password.
Apparently by design, the VBA language does not access the
protection features of the VBA project most likely in
order to thwart password breaking. In other words, there
is no programmatic way to break VBA project protection
using the VBA language. A possible exception is by means
of the Sendkeys method.
In my experience, Sendkeys can be used successfully to
programmatically open a VBA project when the password is
known. However, when not known, using Sendkeys and
the "brute force" method will more likely cause Excel to
crash or, alternatively, will take forever. I personally
have never succeeded.
I know of an alternative method that, based on very
limited experience, is highly reliable. However, I'm not
willing to make this public.
Regards,
Greg
