Trust Publisher

[jwongsf]

Hi all,
I am starting to create Macros, however I have also noticed that when other co-workers use the program, that they have to set their Macro security on LOW, which I really do not want to do Can anyone tell me the steps to take to either becoming a "trusted publisher" so that the end user does not have to reset their computer.
thanks
James

[dominicb]

Good afternoon jwongsf

I could be wrong, but I don't think that the macros will run, no matter how trusted you are. That's the point of having your security set to "Low" - no macros will run. If they were to change their setting to "Medium", then they would be asked each time if they wanted to enable macros.

To get rid of the "enable macros" question, you can use the "selfcert.exe" program that comes with some installations of Office. This gets rid of the "enables macros" prompt, but replaces it with a slightly different warning about the self-cert "publisher", so it all seems a bit pointless.

If your project can be an add-in, then that's the way to go, as once installed it will run without warnings, even if the securty setting is "low".

HTH

DominicB

[Domski]

I wouldn't suggest setting it to low, it always nice to know if a file contains macros so medium is enough so as they just get the prompt.

Depending on what you are doing it could also be worth looking at distributing your code in the form of an add-in.

If you really want to go down the trusted publisher route this might help: http://digital-signs.blogspot.com/20...signature.html

Dom

[Domski]

I could be wrong

And for once you are. It's if the setting is High they won't run.

Dom

[dominicb]

And for once you are. It's if the setting is High they won't run.

"For once": Coo! Thanks.

In that case, what is the question being asked?

Dom (the other one)

[shg]

It's easy, convenient, and free to create a certificate for your own use:

See http://msdn2.microsoft.com/en-us/lib...ffice.11).aspx
http://support.microsoft.com/kb/206637
http://msdn.microsoft.com/en-us/libr...ffice.11).aspx