If you use an excel macro, then that VBA code will live in an excel workbook.

You may not want the code in either the workbook to be separated and you may not
want the code in the customer's workbook either. But the code has to be in a
workbook somewhere.

I think I'd use that third category (not in either of the data workbooks) and
create a new workbook that contains the code. Then just load that workbook when
I wanted to run that macro that separates sheets.



Brad wrote:

I'm not opposed on doing what you are suggesting, but I want to make sure I
know what my options are. I realize that when a workbook is saved the whole
workbook is saved. I guess another way to ask my question is this: Is it
possible and practical to write a VBA to grab a certain sheet from the
"client's" workbook make it part of the workbook that will be given to the
client and that becomes his/hers new workbook. I think this VBA would have
to be outside of Excel in order for this to work.

"Dave Peterson" wrote:

When you save a workbook, you save the whole workbook.

Maybe it's time to make separate workbooks--one for all the common stuff and
lots of individual workbooks (one worksheet each) for each person.

Brad wrote:

I'm going to have an application that will be used by many people. What I
would like to do is to have one sheet (that will have the same sheet name)
that is person specific. When I overly the existing workbook with an updated
workbook to these individuals, the person specific sheet would not be
affected.

Does this make sense, can this be done?

--

Dave Peterson


--

Dave Peterson