Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
How are you experienced developers coping with upgrading your clients?
Most, if not all, of my future changes will be in the Modules, not the worksheets. My current upgrade plan is something like this: 1. Have client open both upgrade and old workbooks. 2. Upgrade will have single sheet containing a command button. Sheet may also contain the macro code or a call to a module routine. 3. Button will copy old workbook sheets (some protected, some not) to upgrade. 4. One copied protected sheet will require adjusting formulas that will retain the identity of the old workbook's filename (gathers data from other sheets). Upgrade code will do this. 5. Last act of upgrade macro is to delete the upgrade sheet (if possible, not sure how this can be done yet if code is contained in the sheet itself). Your input is greatly appreciated.... mike |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Cells User Select Locked after upgrade to Excel 2002 | Excel Discussion (Misc queries) | |||
Ontime procedures | Excel Programming | |||
VBA Sub procedures | Excel Programming | |||
what's wrong with this sub procedures? | Excel Programming | |||
VBA -- procedures as arguments? | Excel Programming |