Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
what i was planning was to have one module contain code that deletes other
modules that contain valuable code. though protected, code can certainly be run, as i do this all the time. if i could unprotect the modules while running this code, i could then delete the other modules (i have the code for this) and have just the output void of the valuable code. of course, i would save it as something else. i can certainly unprotect sheets, so it seems like modules would be available, too. sheets("sheet1").unprotect password:="ok" i'll look into the Add-In and export/import as suggested. thanks, mike allen wrote in message oups.com... The solution I'd recommend is to store proprietary code and worksheets in an Excel Add-In. Alternatively you could import your VBA modules on start up and export them on exiting. See : http://www.cpearson.com/excel/vbe.htm for tips on importing and exporting modules. |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Public, Private, Event modules, Forms modules,,, | Excel Programming | |||
Basic question - modules and class modules - what's the difference? | Excel Programming | |||
When to code in sheet or userform modules and when to use modules | Excel Programming | |||
Unprotecting! | Excel Programming | |||
Class Modules vs Modules | Excel Programming |