Macro template

[Guest]

I do most of my VBA programming in Word. I can create a template with
macros and save it to the Office Startup directory. The macros are
availalble to Word but are not stored in each new document.

I need to do the same thing in Excel. However, If I use the XLStart
directory and save macros in Book.xlt, all new spreadsheets will also contain
the macros/toolbars. I just want the macros to be available to Excel, not
stored in each new spreadsheet. Is the only way to do this through an
add-in? And, if so, it has to be registered through the registry? Isn't
there an easier way to share macros for numerous users?

Thanks for any help you can provide.

 

[Tom Ogilvy]

Use Personal.xls located in that directory (xlstart). Excel works
differently than word.

You can get excel to create it for you by recording an macro and selecting
to store it in the personal workbook.

 

[Guest]

Thanks, Tom. I did see your other entry re: Add-ins, etc. But, what about
if I want to distribute this to other users? The site you provided in your
other response discouraged people from using the personal workbook, as it
would end up wiping out other people's settings

Any other ideas?

 

[Tom Ogilvy]

You never mentioned distributing the workbook. given the limited
information in your questions, personal.xls is equivalent. If you want to
distribute them, then of course you could and probably should use an addin
in that case - but that doesn't make them (macros) easily available to
others. You would need to create a menu so these users can choose a menu
item/button to run the code.

http://www.jkp-ads.com/Articles/DistributeMacro00.htm


http://support.microsoft.com/?id=156942
XL97: How to Create an Add-in File in Microsoft Excel 97


http://support.microsoft.com/?id=211563
How to create an add-in file in Excel 2000

http://www.j-walk.com/ss/excel/tips/tip45.htm
Excel 97: Creating Add-Ins


http://support.microsoft.com/?id=167909
XL: Securing Visual Basic Code in Microsoft Excel

 

[Guest]

Thanks for the info., Tom. I'm getting very close to converting everything
over to .Net so I can avoid all of these differences.