Create statistics

A statistics will be issued at end of program VBA code and
(while processing level "Analysis" always activated)

Display report automatically

CrunchCode generates a report after processing.

It contains the complete list of camouflaged objects
and it is stored as file "en__Final_report.txt" in the folder
(which is located in the folder of the processed Excel file).

Use this option to specify whether the report is automatically
displayed after processing (at processing level "Analysis" is always activated).

Remark: You can also open a report later via
start menu –> "Project..." –> "Reports".

Pocessing in background

No detailed progress output is shown,
only an indicator in the status bar of Excel and in the taskbar.

Attention! It is then NOT possible to interrupt the processing!

Nevertheless, dialog boxes are displayed if this is technically necessary.

Detailed information in progress–display

Gives more detailed information in the progress–display.
A deactivation of this option accelerates the processing something.

After finishing opens VBA editor

During processing CrunchCode must close the VBA editor.
This avoids conflicts with window contents and accelerates the process.
If the option is activated, VBA editor will be re–opened after processing.
Otherwise, it remains closed but can be re–opened by pressing Alt+F11.

Note: The VBA editor also stays closed if the processing level "Analysis"
was chosen because the display of the analysis result has priority.

Generating a retranslation list

Generating of a list of all mappings between camouflaged identifiers and their original names.

This makes it possible to check a camouflaged source code easier
after the occurrence of runtime errors.

See help for "Retranslation" in the menu "Project...".

Compatibility mode Office 2007 / 2010

Some ciphering– and camouflaging–methods cause problems, if the processed project
to be simultaneously used in Microsoft Office 2007 and 2010.

Among others, it can lead to loss of source code togehter with the error message
"Error while loading of .... Would like you to continue with the loading of the project?".

With activation of this option CrunchCode makes certain arrangements
to avoid such compatibility problems.

The thereby resulting reduction in the camouflage effect is small.

Protected mode

Excel keeps after editing of a project a lot of information in memory.

Thereby it can come by a further processing to conflicts
which lead to errors (as for example "Not enough memory").

With activation of this option takes CrunchCode different measures
to avoid such situations as much as possible.

The repeated closing and opening of a project also belongs to it,
whereby superfluous memory contents are deleted.

However, this mode prolongs the process time.

Ignore worksheet access errors

Under certain circumstances, there is temporarily no access
to some information from worksheets.

Possible causes can be:

– inconsistencies in the Excel file
– an internal Excel–Error

If such an error appears, should be tried first
to repair the project (Excel CrunchCode menu, function "Repair").

You can also open the project manually
and instead of "Open" choose "Open and repair".

If the error can not be solved by these measures,
then you have the option to ignore it.

The impact on the program flow are generally low.
Nevertheless, after the processing you should absolutely
check the project for syntax error (compiling) and test it intensely!

Log file

Recording of important actions in a log file.
This enables a more accurate error analysis,
however, lowers the processing speed.

Select this option only after consultation with the CrunchCode support.

If a log file exists, then you can display them.

If you want to delete the file, then open it,
delete the entire contents and save the empty file.
The file is then deleted.

reactivating of messages

CrunchCode makes it possible to suppress messages
if these have no significant impact on the further program flow.

With this function, you can reactivate all ignored messages
so that they will displayed again.

Save report lists in Excel file

Lists, which are generated in reports can be stored in parallel in an Excel file.
This allows an efficient evaluation or processing of this information.

Please note:
Explanatory texts, statistics, and other notes
will NOT transferred into the Excel file!

The file has the name "_Listings.xlsx"
and located in the folder "_CrunchCode\<Excel–file–name>",
which was generated in the folder of each processed Excel file (see above).

The file can also opended with the function "Project..." –> "Excel listings".

All coded names with prefix

You can define max. 4 letters which are prefixed
to every code name, used by CrunchCode.

This option serves above all the assorting of coded names in macro–listings,
which can be called among other things with Alt+F8.

If you, for example, use as a prefix "ZZZZ", the coded names of procedures
are indicated at the end of the macro–listing.

Unified prefixes for all identifiers can reduce the camouflage effect.

To prevent that names of "Public" procedures are displayed in macro–listings,
you can also generate a separate standard module which you denote with the
instruction "Option Private Module".

Implement there all "Public" procedures whose names should not be displayed.

Coded names renew after...

To accelerate the overall process CrunchCode does not generate the camouflaged names
every time the program is run. Instead it relies on a previously–generated pool of names.

This is updated if there is an insufficient number of camouflaged names
for the current project or after a specified number of program starts.

The number of program–starts before the camouflaged names
are updated can be determined.

"now": Enforces updating of the camouflaged names in the next program run.

"Extensive project" from...

CrunchCode treats very extensive projects with certain restrictions.
This prevents problems that occur from insufficient memory.

For simplicity, the size of a "large project" is based on
the total number of the source–code lines.
The actual memory–requirements is determined among others by the number of

– formulas and functions
– pictures and charts
– declarations and data–structures

Should projects be repeatedly classified as "large" but these do not generate
memory problems, then the number of source–code lines can be increased
or decrease in the opposite case.

Factor for lists–width

With this value CrunchCode determines the optimal width of lists in dialogs.

If row contents of lists in dialog boxes are displayed incomplete,
then increase this value in small steps.

Conversely, you can reduce the value when the dialog lists are displayed unnecessarily broad.

Standard value: 47


Setting the editor program, which shows all reports
that CrunchCode creates. It will usually be Windows–Notepad.

Only choose an pure editor program (like e.g. Notepad++),
not a text processing program (like e.g. MS Word)!

All issued lists are saved in a subfolder called "_CrunchCode\<Excel–file–name>",
which is located in the folder of the processed Excel file.

Project: D:\VBA\myproject.xlsm
CrunchCode folder: D:\VBA\_CrunchCode\myproject.xlsm\...

delayed display:

CrunchCode  jumps in some lists to certain text lines.

If the editor takes a little more time for the full display of the text,
then such a jump fail sometimes.

In this case this option should be activated.
Then CrunchCode waits for the displaying of the entire text.

Keyboard shortcut for "Go to":

Keyboard shortcut in the editor, that triggers the command "Go to (line)"
CrunchCode requires this information in order to display passages in the source code.

For a modification click into the input field and press the new key combination.

Allowed: Ctrl, Shift, Alt in combination with 0..9, A..Z
Standard value: Ctrl+G


Changing of the program language.

For each language is a language file required (type *.lng),
which needs to be stored in the CrunchCode–program folder

The names of the there existing language files are displayed in this list.

These text files consist of a list of identifiers (IDs)
and the associated language–specific translations in the following format:

    ... \
    ...  > text to be displayed
    ... /

For each text output in CrunchCode there is a special ID,
whose subjacent text is displayed.

You can adapt the language files any time to your own needs.
Thereby, the following rules are to be observed:

– all text lines that follow an ID (up to the next ID) belongs to its text
  and can be changed freely

– however, the following contents may NOT be changed:

**xxx ID's (identifiers)
<_xxx> wildcards for words
<1>...<9> wildcards for values
<<xxx>> wildcards for links

– for comments, their content will be ignored, the following options are available:

; only at the beginning of the line: Entire line is a comment

#...# comment within a line – the content between them is ignored
if missing the final #, then the content is ignored until the end of the line
several successive ## are treated like a single #

– for certain characters must be used special characters:

^ tabulator
° blank line
~ the character Ż (Underlining of a preceding line)
@ the character #
§ only at the beginning of the line: Semicolon,
that shall not be the beginning of a comment–line

The listed here special characters themselves cannot be used.

Color scheme

Selection of a predefined color scheme for the user interface.

All available schemes are stored in the file "ColorSchemes.ini",
which is located in the CrunchCode folder

You can customize any color scheme or generate new schemes.

To test after changing the color–scheme,
click the reload button.

Globally blocked keywords

Opens a user–defined list of keywords that should not be camouflaged in ANY project.

Debugging instructions

Opens a user–defined list of debugging instructions, which typically find a use
while the treatment of a project and they should be neutralised before the processing
because they can give hints to sensitive internals and code positions.

CrunchCode folder

Opens the CrunchCode program folder, where also the keywords– and language–files are saved.