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

how about have the upgrade sheet make a copy of iitself and insert into the
eisting workbook...thats all the "installupgrade" button does.Then get your
client to run the upgrade from within the existing workbook and delete the
new upgrade workbook.The next time you have an upgrade delete the old upgrade
sheet before inserting the new one.
howzat?
--
paul
remove nospam for email addy!



"mike" wrote:

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

That would mean all my code would reside in a sheet. From what I've
read, that is not desirable. Most all code is in a general module. Is
there a way to simply replace a module?

i thought only the specific upgrade stuff would reside on the sheet.I dont
know if that is desireable or not it was just an idea.I beleive there is a
way to rewrite code with code.....Its above my head tho.I jstick to upgrading
certain parts of sheets
Just trying to put some ideas out there
--
paul
remove nospam for email addy!



"mike" wrote:

That would mean all my code would reside in a sheet. From what I've
read, that is not desirable. Most all code is in a general module. Is
there a way to simply replace a module?

You can replace a module via code.

With ActiveWorkbook.VBProject.VBComponents
.Remove .Item("OldModule")
.Import Filename:="C:\NewModule.bas"
End With

This code, of course, should not be in the module that is being
deleted.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com


"mike" wrote in message
oups.com...
That would mean all my code would reside in a sheet. From what
I've
read, that is not desirable. Most all code is in a general
module. Is
there a way to simply replace a module?

That certainly is better than what I had planned. Unfortunately,
providing the module in a BAS file exposes your code. I know. I've been
told just how unsecure securing my code with a password is! Still, it
would be nice to be able to simply import the module directly from a
workbook rather than a text file.

I surmise that I could include an upgrade function in a separate module
in an upgrade workbook with new code and a control that activates the
function. Otherwise the function is dead code. Guess I need to plan a
strategy!!

Thanks for everyones input. I'll keep looking back here in case new
ideas are posted.

best regards,
mike