Macro Placement

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Macros and VBA code in general are not well suited to being distributed. COM
addins are a far better choice for that.

In your Outlook VBA project put your macro in a code module of its own. Use
File, Export to export that module to the file system. Send it to whoever
and have them open their VBA project and Import the module. They then have
your macro.
 
I have to admit, my work with macros, especially those revolving around
Outlook is rather limited. Is there a way for me to convert the macro to
VBScript from within the Editor supplies in Outlook. I do not have Visual
Studio or any other such software available to me here, so my ability to
manipulate code is somewhat limited. If there is a handy way for me to
convert the file then I can get it onto a network drive to allow people to
access it.
 
A VBScript file is just a text file with a .vbs extension. Create it in Notepad. The main differences between VBA and VBScript are that VBScript doesn't support typed variable declarations or ol* constants. You'll also have to instantiate your Outlook.Application object.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
That seems to have helped with the Object Library not Registered error, thank
you.

I'm still getting problems with my Switchboard though. "Error: 429 ActiveX
Component can't create object"

The error is on line:
Set con = Application.CurrentProject.Connection

with .Connection highlighted.

In this database the following references are checked:
Visual Basic for Applications
Microsoft Access 11.0 Object library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.1 Library
Active DS Type Library
Active Setup Control Library

Any thoughts on what might be causing this as well?
 
Did you mean to post this in an Access forum? It doesn't seem to have anything to do with Outlook.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Back
Top