Distributing VBA projects is discouraged, not that it's buggy but it
overwrites any macros the user has. Signed projects would need to have the
signature installed on the user machine.
For a simple macro trading the code module around is probably the easiest
way.
COM addins are the most robust solution for wider distribution but they are
more complex to develop and require a development platform outside of VBA.
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
"Jordan" <Jordan[ at ]discussions.microsoft.com> wrote in message
news:6B9D6454-1B41-4BDD-B0A2-D61C99CDB06B[ at ]microsoft.com...
[Quoted Text] >I wrote a small macro that I would like to have other people in the office
> use. I read some articles one of which said you can copy the project but
> it
> has some known bugs. We also came up with being able to export the module
> and importing on another users machine. This seems to work fine.
>
> I just wanted to know if there is a better way to handle this and if a com
> add-in (which I know nothing about) is the way to go, would there be code
> already written for doing this.
>
> I do have the project signed, if that makes a difference.
>
> Any and all insight will be greatly appreciated.
>
> Thanks.
|