Thread: Macro Placement
View Single Post
  #2  
Old September 15th 06, 03:10 PM posted to microsoft.public.outlook.program_vba
Sue Mosher [MVP-Outlook]
external usenet poster
 
Posts: 11,651
Default Macro Placement

There is no supported way to distribute Outlook VBA code. What about converting it to VBScript and putting it on a network drive where people can run it? Or, since you're in an Exchange environment, incorporate it into a message form published to the Organizational Forms library, similar to the form at http://www.outlookcode.com/d/forms/holiday.htm

--
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

"RSteph" wrote in message ...
I've built a small macro in Outlook to handle managing some settings for
contact lists. Specifically placing 4 different "Public Contact Lists" into
the favorites folder, and making them viewable in the Address Book. I've
tested the macro on my own machine and it works perfect.

Now I would like to make the macro useable to the rest of the people in my
office. So that they could simply run it, rather than my halving to go around
to each person and alter the settings, or have them do it themselves. (The
office has a diverse level of computer knowledge).

The only way I know of to do this is to send the macro, as a file, via
e-mail to everyone, have them save it in the appropriate folder, and run it.
This option causes problems as it requires changing macro security level, and
placing a file in a hidden folder. I've tried turning the macro into a VB
executable, but I'm having problems getting it to run, and I don't have the
appropriate software at work to make changes to the VB project.

Is there another, better, option that would accomplish this task? Is there
perhaps a way for me to put this macro on the Administrator account, and then
somehow make it accessible to other people accounts; or perhaps put it on the
mail server, and force run it for everyone's account?

Any advice would be greatly appreciated.

Ads