The user may have several workbooks for various projects. They all have
exactly the same template and input requirements. However, the business
process will change over the next few months as we implement new features.
The template will not. The user does not want to have to copy and paste from
a previous workbook to a new template simply necaue some code changed..

There are several hunderd users involved. They want to use EXCEL as if it
is a "smartclient".

Wes

"Bob Phillips" wrote in message
...
Wes,

If it will only be the same workbook being worked upon, why do you need
to
separate them. Why not keep them together?

--

HTH

Bob Phillips

"Wes Jester" wrote in message
...
I am fairly new to using VBA and have a question regarding maintenance
of
the VBA code

1. I need to separate the execution of the VBA from the spreadsheet.
The
application will probably get updated often, and the user will not be
using
a new template, simply opening the saved workbook. Is there a method I
can
use in workbook_activate, or some other event, to "load" the current set
of
modules or at least point to a location where a "master" may be kept?


If you wish, you can e-mail me direct at