Sorry... you're not going to get much help here.
People who write VBA code  for a living really,really,really hope
that it isn't that easy to break into their code.
Additionally, no one here wants to accept the responsibility of
giving someone access to VBA code that he/she does not own.
I've been in the same situation before. That's why my "Development"
copy is kept separate from the "Released" copy, and is unsecured.
(VBA-wise, but it's located in a secured folder)
When I "release" the macros, I password  protect it at that time.
I'm sure I've seen some hacker code out there that can do it,
but from a professional standpoint, I hope it's not too easy to get!
sorry,