> Why would a macro be out of the question? That's what VBA does -- allows the user to run macros.
>
[quoted text clipped - 36 lines]
> >
> > pk
Most of those options are handled by registry values that Outlook caches during the current session. So even if you change the registry value, Outlook won't use it.
Copying VBAProject.otm will overwrite any macros the user already has, and the code still won't work until the user touches the VBA environment at least once.

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
>I would just copy the VBAProject.otm file to all of the workstations
> for distribution. I swear I read something that said options in the
[quoted text clipped - 33 lines]
>> >
>> > pk
philip.kluss@gmail.com - 03 Aug 2006 15:30 GMT
I found a post from a few years back on this newsgroup that solves my
problem. (not the distribution aspect, but i'll deal with that.) The
code is very simple. This solution is great because I can keep my
previous forwarding options intact.
-------------------------------------------------------------------------
Rather than forwarding, this code creates a new message with the
selected
message included as an attachment:
Dim objAtts As Outlook.Attachments, objMsg As Outlook.MailItem,
objNew
As Outlook.MailItem
Set objMsg = ActiveExplorer.Selection.Item(1)
Set objNew = Application.CreateItem(olMailItem)
Set objAtts = objNew.Attachments
objAtts.Add objMsg
objNew.Display
--
Eric Legault, MCSD
ADAPSYS - http://www.adapsys.ca
-------------------------------------------------------------------------
> Most of those options are handled by registry values that Outlook caches during the current session. So even if you change the registry value, Outlook won't use it.
>
[quoted text clipped - 45 lines]
> >> >
> >> > pk