Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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 |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Macro functionality | Excel Worksheet Functions | |||
Macro inhibits Excel Functionality (i.e., No Longer Able to Use Co | Excel Programming | |||
Basic Excel functionality collides with VBA code. | Excel Programming | |||
How to run Macro functionality for a protected worksheet | Excel Programming | |||
Help with Countrows functionality within a Macro | New Users to Excel |