I'm also considering doing something like a Compare add-in I picked up
somewhere. When the add-in is enabled, something is added to the Tools menu
for execution. I'm thinking that when we move to Office 2007, this will be
in an XLAM and I'll have to convert. OK, I know I've asked too many
questions for one thread so will stop for now.

Barb Reinhardt

"Barb Reinhardt" wrote:

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