Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have created an application that generates and manages multiple
workbooks, each of which gathers inputs from a separate division. All inputs are put together into an "Main" workbook. All these workbooks are created dynamically once for each month of the year. I have written the VBA code in a separete workbook which has only configuration information. I would like to compile this code so that it becomes tamper proof. Any fiddling can have massive negative consequences. So how do I - "freeze the code' - ' make it unaccessible unless actually required' - can this "mother workbook" itself be hidden so that config info is only accessible through a utility designed for the purpose ? Jai |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Compiling Excel 2003 application written in VBA 6.0 Code | Excel Programming | |||
Problem in compiling code containing "$" char | Excel Programming | |||
Compiling Excel VBA code increases workbook file size! | Excel Programming | |||
Compiling vba code as stand alone exe | Excel Programming | |||
Add not compiling | Excel Programming |