All Outlook macros are kept in one file, VBAProject.OTM. You cannot
have a signed macro and another one unsigned. You either sign the VBA
project or you don't. You can export modules that have macros in them
and the user can import those .BAS files. Or you can distribute an
entire .OTM file, which would overwrite any previous .OTM the user
had.
Signing a VBA project is something the user has to do with a
certificate that is valid on their computer. That can be a commercial
code signing certificate from an authority such as Thawte or Verisign
or it can be the free certificate generator included in Office
(SelfCert.EXE). If the certificate is installed on the user's computer
they can install it in the VBA project using the Tools, Digital
Signature menu and then trust the certificate in the UI from Tools,
Macros, Security. That menu also lets you set macro security to High,
Medium or Low.
The best way to distribute code is to develop a COM addin and
distribute that.
I'd suggest starting at
http://www.slipstick.com/dev/index.htm and
looking at the topics for VBA and COM addins to get a handle on all
this.
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Lead Author, Professional Outlook 2000 Programming, Wrox Press
Lead Author, Beginning VB 6 Application Development, Wrox Press
Attachment Options
http://www.slovaktech.com/attachmentoptions.htm
Extended Reminders
http://www.slovaktech.com/extendedreminders.htm