Activating a macro from another file for advanced security protection

[John Jok]

As I said, the macro code in the template is only available to the document if the template is available. That should not be an issue if you save the template in your local templates folder since, even within workgroups, other users don't ordinarily have such access.

But if you don't want to do that, simply save the blank as an ordinary document in your own folder and make sure both documents are open if you want to run the macro and that the document you want to work on is the active one. The only inconvenience is that you'll need to run the code from the VBE instead of from within the active document.

As for VBA project security, contrary to what you say it is fairly robust. Your deprecation of it, combined with your secretiveness about your code, suggests there is another motive. As an employee or contractor, any code you might develop is the intellectual property of the organization you're working for unless there is an employment/contract clause explicitly saying otherwise.

Thanks again and correct me if I am wrong but I don't quite see how my colleagues will be able to run the code if I'll have to run it from VBE.


Now, the VBA project security I was referring to has to do with the passwords.
I've done some research and they say it's quite easy to crack a password-protected document (including the access to VBE) with a brute force method.


Last but not least, allow me to defend my secretiveness and tell you that my position in the company is a Service engineer and not a programmer, even though we have plenty of them.
I've requested in the past from the company's top management to build a program like this, but the priorities are always different.
I am doing this for my myself and my colleagues you know. Eventually, if the management appreciate the easiness of automating trivial things and the great effort I've put into it, I have no objection of giving it to them. Chances are however that probably they will not. In that case, I'd rather keep at least the code for myself.


Oh, and one more thing. I am doing this in my spare time you know. Officially it doesn't exist, and it cannot exist since they will blame me that I leave my normal job behind.
Until the project is up, running and recognized by the company as it should, I'd rather keep it that way.


Thanks.