Ditto. I like getting the prompt at startup. It lets me know for sure that VBA did indeed kick in.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Ken Slovak - [MVP - Outlook]" wrote in message ...
What I was thinking of wasn't registering it using IE, but after creating
the selfcert and setting the VBA project to use that cert to see if it shows
up in the trusted publishers list under Trust Center.

To tell the truth I usually set my macro security to prompt rather than
using a certificate. In my experience there are problems when you sign the
VBA project, like if you sign it and then change it and re-sign you get tons
of prompts to save. It was really bad on Outlook 2003 and earlier, so I got
out of the habit of signing the code.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Dan" wrote in message
...

"Ken Slovak - [MVP - Outlook]" wrote in message
...
I'm not positive, but my guess is that the extra time with the selfcert
certificate is an attempt at validation from a certificate root
authority.

I'd be curious if you add the selfcert certificate to your trusted
publishers list if that helps at all.

hi ken,
that's what I tried. I believe I mentioned it below as well..
I exported the selfcert certificate, deleted it and then importet it into
the Trusted Root Certification Authorities Store. that actually works (I
was a little surprised on that). I could even select it in the VBA editor
as digital signature. then I exit the VBA editor, still no complaint from
Outlook.

But as soon as I exit Outlook, it just tells me that there was a problem
and that it removed the digital signature.. I don't recal the exact pop up
message, though.

dan