I've got a personal workbook where I put in all my new code so that it
can be available to all my other workbooks when I start up. However,
if I end up wanting to release a particular workbook, I have to
release my code library workbook plus the application workbook. What
are some good strategies for dealing with this problem?

Don't use a workbook named personal.xls (or personal.xla). If you share this
same workbook with others, then those users may have to decide to use your
version of personal.xl* or their own.

Call it something nice:
FormidoUtils.xls (or .xla)

I'd save it as an addin (*.xla) and store a single copy in a nice common network
location and refer to that location via its UNC path
(\\aaaa\bbbb\formidoutils.xla). I wouldn't use a mapped drive--others may not
connect using the same letter.

If that's not possible, I'd ask all the users to store the addin in a folder on
their C: drive--and make that folder name exactly the same for all users:

c:\Formido\formidoUtils.xla

Then any UDF used in a cell will always find the function in the same
location--it'll make working with links and users easier.

And if you have subroutines that need to be run from that addin, you'll have to
give the user a way to run them.

For additions to the worksheet menu bar, I really like the way John Walkenbach
does it in his menumaker workbook:
http://j-walk.com/ss/excel/tips/tip53.htm

Here's how I do it when I want a toolbar:
http://www.contextures.com/xlToolbar02.html
(from Debra Dalgleish's site)


"(E-Mail Removed)" wrote:
>
> I've got a personal workbook where I put in all my new code so that it
> can be available to all my other workbooks when I start up. However,
> if I end up wanting to release a particular workbook, I have to
> release my code library workbook plus the application workbook. What
> are some good strategies for dealing with this problem?

--

Dave Peterson

On Jul 19, 3:15 pm, Dave Peterson <peter...@verizonXSPAM.net> wrote:
> Don't use a workbook named personal.xls (or personal.xla). If you share this
> same workbook with others, then those users may have to decide to use your
> version of personal.xl* or their own.
>
> Call it something nice:
> FormidoUtils.xls (or .xla)
>
> I'd save it as an addin (*.xla) and store a single copy in a nice common network
> location and refer to that location via its UNC path
> (\\aaaa\bbbb\formidoutils.xla). I wouldn't use a mapped drive--others may not
> connect using the same letter.
>
> If that's not possible, I'd ask all the users to store the addin in a folder on
> their C: drive--and make that folder name exactly the same for all users:
>
> c:\Formido\formidoUtils.xla
>
> Then any UDF used in a cell will always find the function in the same
> location--it'll make working with links and users easier.
>
> And if you have subroutines that need to be run from that addin, you'll have to
> give the user a way to run them.
>
> For additions to the worksheet menu bar, I really like the way John Walkenbach
> does it in his menumaker workbook:http://j-walk.com/ss/excel/tips/tip53.htm
>
> Here's how I do it when I want a toolbar:http://www.contextures.com/xlToolbar02.html
> (from Debra Dalgleish's site)
>
> "form...@gmail.com" wrote:
>
> > I've got a personal workbook where I put in all my new code so that it
> > can be available to all my other workbooks when I start up. However,
> > if I end up wanting to release a particular workbook, I have to
> > release my code library workbook plus the application workbook. What
> > are some good strategies for dealing with this problem?
>
> --
>
> Dave Peterson

Thanks, that was extremely helpful.

-mwt