I'm familiar with workbook events in a specific workbook. Can you direct me
to how I'd do that with an Add-In?

Thanks,
Barb Reinhardt

"Peter T" wrote:

I would go with your idea putting all your code in an addin. Not why sure
you would need any references at all (I assume you are talking about Tools,
Ref's). Only reason to do that is to be able to call code in the referenced
workbook as if it is in the same workbook; presumably that scenario would
not exist if there is no code in the deployed workbooks.

You can trap events of any or all open workbooks at sheet or workbook level
from within your addin (in addition to application level events), if that's
an objective.

Regards,
Peter T


"Barb Reinhardt" wrote in message
...
I'm working with a group that has vanilla flavored workbook (no code) that
they want to deploy. At some time in the future, they want to be able to
add code to that workbook.

The options I can come up with a

1) Use functionality such the stuff on Chips site about Programming in
the
VBA editor to add the code to the now vanilla workbook. The problem I
can
forsee is that the macros would still need to be enabled each time the
workbook is opened. I don't want to recommend that people set their
security to LOW. We're looking at digital signatures as well, but as I
understand it the code would need to be signed after it's in the workbook
and
I"m guessing that can't be done programmatically.

2) Put the code in an Add-In that's distributed later. I've only done
this once and had to select a referece to the Add-in in the VBE. I'm
thinking that we can decide on the name for the Add-in now and set the
reference to it. When the add-in is deployed, the reference will already
be
set and it'll be ready to go.

Comments/Suggestions. Am I completely on the wrong track?

Thanks,
Barb Reinhardt