Project operations




Recover

Sets the selected project back to its original status.

If this button is not available, then there exists no backup for this project
or necessary to that end data could not be found.

CrunchCode performs a reset automatically by every start of a processing
if the project was already processed (recognizable by the marker
"< protected by www.CrunchCode.de – DO NOT CHANGE OR REMOVE THIS LABEL! >").

Note: Should EXTERNAL text files have been processed in a previous program run,
then they will also be reset their initial state.

WARNING!
ŻŻŻŻŻŻŻŻŻŻ
ALL OF THE CHANGES MADE TO THE SOURCE CODE
WILL BE LOST!

CrunchCode saves all the informations, process data and recovery files
in a subfolder with the name

"_CrunchCode\<Excel–file–name>",

which is located in the folder of each processed Excel file.

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

DO NOT DELETE THE DATA IN THIS FOLDER MANUALLY!
Otherwise your project cannot be reset.
(use for this "Project... –> Settings –> Delete")

ALWAYS BACKUP YOUR PROJECT!
CrunchCode has numerous safeguards to prevent data loss.
However, absolute security cannot be guaranteed.


Save

Saves changes to the current project.

CrunchCode basically opens all projects without performing auto–procedures.
In certain cases this can lead to the fact that the storage of changes
on normal way (Ctrl+S or save symbol) is temporarily not possible.

Then use this function to save changes in your project.


Files –> Reports

Displays all reports and lists that have arisen during the previous processing
(including final report).

These are located in the folder "_CrunchCode\<Excel–file–name>",
which was generated in the folder of each processed Excel file (see above).


Files –> Excel listings

Certain dialogues allow the export of the listed content into an Excel file
that you can open with this function.

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).


Files –> Working directory

Displays the working directory of the current project ("_CrunchCode\<Excel–file–name>").


Settings –> Export

Saves all settings of the current VBA project in a separate file ("*.cci").

Therewith you can save different processing options
for the same project and restore it at a later time
or transfer it to another project.

Global program settings ("CrunchCode options") are not saved.


Settings –> Import

Loads all saved settings from a separate file ("*.cci")
and applies them to the current VBA project.

Attention!
ALL current settings will be overwritten!

Global program settings ("CrunchCode options") are not changed.


Settings –> Delete

Resetting and deleting project Information

CrunchCode stores a lot of information about the project and its processing.
These serve to restore the original status, debugging the finished project, etc.

Under certain circumstances it may be necessary to delete such information:

– if the processing is completed and
  a restoration of the original state is no longer necessary

– when a fatal error occured and
  therefore a further processing of the project is no possible

Therefor you can specify in the following dialog, which informations shall be deleted.


VBA modules –> Export

Exports all existing modules in the VBA project into a common folder.
The folder should be empty so that it is not possible for them to be mixed up with other modules.
The modules are saved there as text files that can be processed.


VBA modules –> Import

Imports VBA modules from a folder.

Warning!
ALL modules located in the specified folder will be imported!


TIP: With CrunchCode you can also edit VBA modules
that are exported from other programs:

– create a new blank Excel file
– load the required modules into this file using the import function
– save the Excel file
– process the VBA project with CrunchCode
– save the processed VBA modules using the export function


VBA modules –> Modules exclude

Excludes VBA modules from processing.


Debug –> Retranslation

This function serves the simplified checking
of the camouflaged source code (e.g. after runtime errors).

She generates for each VBA module a text file,
whose structure is identical to the module,
but in which all code names have been replaced by their original names.

In the project itself no changes are made.

In addition some code sections are commented out with  '_generated by CrunchCode_
where only located auxiliary functions, which were generated by CrunchCode.

The text files are stored in folder
"_CrunchCode\<Excel–file–name>\Retranslation",
which is located in the Excel file folder.

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

Each text file will be named using the following pattern:

<camouflaged module name> (<original module name>).<module type>.vbs

Example: xZqOuiX (Module3).bas.vbs

The extension *.vbs serves only to enable a syntax highlighting in certain editors (e.g. Notepad++) .

Attention!

The *.vbs files are not executable!

The retranslation is NOT A RECOVERY of the VBA project!


Debug –> E–Mail support

This function serves the CrunchCode support
and prepares the current VBA project to send via E–Mail.

This is necessary when a processing error appeared whose cause
can be determined ONLY with the help of the original source code.

CrunchCode prepares an email with a ZIP file attachment
that contains the project, the used program settings
as well as perhaps to the project associated external files.

You can edit this message before send.

For the protection of your intellectual property
is created only a copy of the project
in which following elements are deleted:

Worksheets:
– texts, numbers and comments
– texts in buttons and graphical elements

VBA–Code:
– blank lines
– comments
– code structuring ("indentations")
– captions of UserForms

An in this manner prepared project contains still
all elements necessary for a fault location,
but a contentual analysis is very difficult.

Your algorithms and technologies remain in this way extensively protected.

WE GUARANTEE:

YOUR SOURCE CODE WILL

– KEPT STRICTLY CONFIDENTIAL
– NOT COPIED
– NEVER MADE ACCESSIBLE TO OTHER PERSONS
– DELETED IMMEDIATELY AFTER A SUCCESSFUL ERROR ANALYSIS