You could put the macros in an XLAM (addin) that also loads a custom
menu. This makes the current code always contained in a single
(distributable) file, and obviates the need for your period files to
contain any code at all. Just redistribute any new version of your
addin as needed!

Normally, I'd 'tag' the project workbooks so the addin knows which
files to make its menus available to. I use a template for the fiscal
period file so a new one can be started in new fiscal periods.

So then...

Addin:
- contains all code/forms/features/functionality
- creates/destroys its own custom menus at startup/shutdown
- only enables menus when one of its project files is active

Template:
- reusable project file used by the addin for dedicated tasks
- new template created by the addin for each new fiscal period

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion