Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• Creating library files to be called by EXE
• Distinguish between WBTs and WBCs
• Encode for Calls from EXE files
• How to Retain Parameter Values in Called WBCs
• Passing Info from WinBatch EXEs to Calls
• Passing Parameters between Called WBTs
• Testing whether or not a Call was Made

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Encode for Call's from EXE files

Keywords:        encode call wbt exe compile compiler encrypt 

---

Encode for Call's from EXE files

This option creates an encoded WBC file. You need to use this option when you are Calling secondary WBTs files from a main WBT, and now want to compile all the files for distribution.

All the "Call"ed WBT files must be compiled with the "Encode for Calls from EXEs" option in the Compiler. WBT files compiled with this option will end up with the *.WBC file extension. Go back into your original main WBT file, change the Called WBT file names to *.WBC file name extensions, and recompile the main WBT as either a large standalone or small EXE.

If your code has a Call to another WBT file, the called WBT *must* be compiled with this option. Otherwise, when you run your EXE, you will get an "Encrypted/Encoded Verification Failed" Error.

Encoded WBT files provide the following:

• Source code is protected from unauthorized or accidental modification.
• Encoded WBT files (which become WBC files) may be CALL'ed from compiled EXEs.

Note: When you compile your file, your Target filename will need a different name from the original filename. You cannot compile a file to its own name without corrupting the file.

---

Article ID:   W12785

Filename:   Encode for Calls from EXE files.txt

File Created: 2003:03:20:10:25:56

Last Updated: 2003:03:20:10:25:56