Distributing an add in

This is really a two fold question.

First, I have a macro that forces a custom header/footer to a page in one
file. Is it possible for me to export this to .xla, and then have it
autoload into other files?

Basically I do not want to have to manually put this code into the vba of
each file. Is my only option a dll?

I surely wouldn't want your macro to change my headers/footers for all my
workbooks. But if you gave me an addin that I could run on demand, I might
actually appreciate it.

If that appeals to you, you may want to take a look at how John Walkenbach does
it for his AddPath addin:
http://j-walk.com/ss/excel/files/addpath.htm

Daniel McCollick wrote:
>
> This is really a two fold question.
>
> First, I have a macro that forces a custom header/footer to a page in one
> file. Is it possible for me to export this to .xla, and then have it
> autoload into other files?
>
> Basically I do not want to have to manually put this code into the vba of
> each file. Is my only option a dll?

--

Dave Peterson

Thanks Dave, got me in the right direction.

To paraphrase, if I save this macro as a .xla file, I should be able to
have the clients enable it through the add in tool, correct?

Is the internal list of available add in's kept in the registry? I wouldn't
want to enable the add in for the client, but it would simplify things if the
add in was already there, and the client could simply click the check box.
--
Dan McCollick


"Dave Peterson" wrote:

> I surely wouldn't want your macro to change my headers/footers for all my
> workbooks. But if you gave me an addin that I could run on demand, I might
> actually appreciate it.
>
> If that appeals to you, you may want to take a look at how John Walkenbach does
> it for his AddPath addin:
> http://j-walk.com/ss/excel/files/addpath.htm
>
> Daniel McCollick wrote:
> >
> > This is really a two fold question.
> >
> > First, I have a macro that forces a custom header/footer to a page in one
> > file. Is it possible for me to export this to .xla, and then have it
> > autoload into other files?
> >
> > Basically I do not want to have to manually put this code into the vba of
> > each file. Is my only option a dll?
>
> --
>
> Dave Peterson
>

Yep. The users can install it via Tools|Addins.

And if you don't know where the addin will be kept, it might be better to let
the users decide where they should keep that file.

(And yes, the windows registry keeps track of the addins that show up in that
dialog and also whether they're checked or not.)



Daniel McCollick wrote:
>
> Thanks Dave, got me in the right direction.
>
> To paraphrase, if I save this macro as a .xla file, I should be able to
> have the clients enable it through the add in tool, correct?
>
> Is the internal list of available add in's kept in the registry? I wouldn't
> want to enable the add in for the client, but it would simplify things if the
> add in was already there, and the client could simply click the check box.
> --
> Dan McCollick
>
> "Dave Peterson" wrote:
>
> > I surely wouldn't want your macro to change my headers/footers for all my
> > workbooks. But if you gave me an addin that I could run on demand, I might
> > actually appreciate it.
> >
> > If that appeals to you, you may want to take a look at how John Walkenbach does
> > it for his AddPath addin:
> > http://j-walk.com/ss/excel/files/addpath.htm
> >
> > Daniel McCollick wrote:
> > >
> > > This is really a two fold question.
> > >
> > > First, I have a macro that forces a custom header/footer to a page in one
> > > file. Is it possible for me to export this to .xla, and then have it
> > > autoload into other files?
> > >
> > > Basically I do not want to have to manually put this code into the vba of
> > > each file. Is my only option a dll?
> >
> > --
> >
> > Dave Peterson
> >

--

Dave Peterson