1 I have written a macro
2 I have signed it
3 I have chosen to 'always trust' my own macros on this terminal
4 I want other users in my company to be able to choose to always trust me
on their terminals.
5 I believe that in self-signing my macro I made a private key, which is
only on my terminal, hence nobody else can choose to always trust me. (With
security on High, they cannot even enable my macros one-time-only)
6 How do I either share this private key with the other terminals in the
copmany (top choice), or
7 How do I use 'Microsoft Certificate Server'? Which I have heard a little
about but don't know how to use (I am intimidated by this suggestion).

Notes:
A Of course, It is not OK to have all the users in the company on medium
security and OKing my macro every time.
B There's no way I'm getting a verisign (cost-value payoff).
Also, I don't really want a 'dodgy' fix, or security bypass, I want it kosher.

Neilio,

I can't test this for your company configuration, but in principle:

1. use selfcert to create your own certificate
2. sign your vba project from the tools menu in the vbe
3. distribute the project as an addin rather than a workbook.

Robin Hammond
www.enhanceddatasystems.com

"Neilio" wrote in message
...
1 I have written a macro
2 I have signed it
3 I have chosen to 'always trust' my own macros on this terminal
4 I want other users in my company to be able to choose to always trust me
on their terminals.
5 I believe that in self-signing my macro I made a private key, which is
only on my terminal, hence nobody else can choose to always trust me.
(With
security on High, they cannot even enable my macros one-time-only)
6 How do I either share this private key with the other terminals in the
copmany (top choice), or
7 How do I use 'Microsoft Certificate Server'? Which I have heard a little
about but don't know how to use (I am intimidated by this suggestion).

Notes:
A Of course, It is not OK to have all the users in the company on medium
security and OKing my macro every time.
B There's no way I'm getting a verisign (cost-value payoff).
Also, I don't really want a 'dodgy' fix, or security bypass, I want it
kosher.

Dear Mr Hammond,

Thankyou for your reply. I understand you refer to distribution of this as a
program, a tool, not a workbook. (Like you say, xla not xls). I have a
workbook, containing macros, that I want to sit on my server, and allow all
users to access and modify.
That is, not distribute

Sincerely, Neil

"Robin Hammond" wrote:

Neilio,

I can't test this for your company configuration, but in principle:

1. use selfcert to create your own certificate
2. sign your vba project from the tools menu in the vbe
3. distribute the project as an addin rather than a workbook.

Robin Hammond
www.enhanceddatasystems.com

"Neilio" wrote in message
...
1 I have written a macro
2 I have signed it
3 I have chosen to 'always trust' my own macros on this terminal
4 I want other users in my company to be able to choose to always trust me
on their terminals.
5 I believe that in self-signing my macro I made a private key, which is
only on my terminal, hence nobody else can choose to always trust me.
(With
security on High, they cannot even enable my macros one-time-only)
6 How do I either share this private key with the other terminals in the
copmany (top choice), or
7 How do I use 'Microsoft Certificate Server'? Which I have heard a little
about but don't know how to use (I am intimidated by this suggestion).

Notes:
A Of course, It is not OK to have all the users in the company on medium
security and OKing my macro every time.
B There's no way I'm getting a verisign (cost-value payoff).
Also, I don't really want a 'dodgy' fix, or security bypass, I want it
kosher.