macropod - huh? With no desire to hijack the thread, but could you elaborate on "the distinction is lost on many users"?
We are talking about someone trying to look at code. Not look at a list of available macros in the macro dialog, but
opening up the VBE to look at code.
I am having trouble seeing the distiction being lost on anyone.
Oh....wait a minute. Right. Sorry. I use the macro dialog so rarely, I forgot there is an Edit button, which of course does open the VBE.
OK. Point accepted. If it is not listed, then there would be no Edit for it. Although, Edit
for any other macro would open the VBE. In which case...Private or not, there is the code. So I am not completely convinced of the usefulness. It would take very little to be able to see the code. Simply click Edit for ANY macro.
With a loaded template (that holds the code) the project is unviewable. If the users does not have open rights permissions, then they can not open the file and see the code. A global template/addin, password protected at the VBE level, write-protected at the OS level, sitting in a folder with no user Modify permissions at the Permissions level - that is about the best you can do.
Is that crackable? Of course it is. However, your user is going to have to be pretty darn good. They would have to crack Admin level access to the folder/file permissions, then crack the password in the VBE.
Frankly, I have a hard time seeing anyone who can do that being much interested in dinky VBA code in a document. They would have far more interesting things to play with.
Gerry
My paintings and sculpture