| Playing with Scan Codes |
| QTIPS - Compiling Protection Code |
| QTIPS - Invalid Code and Command |
| QTIPS - Code/Command Help |
| Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd) |
| Vroom |
| QTIPS - Replacing GAS.BAR routine during PERFORM "SELECT" |
| QTIPS - Extended Select BY |
| QTIPS - PERFORM Arguments and FMT Specifications |
| What's New (and un(der)documented!) In 2.12 |
| VERBatim - V15 |
| QTIPS - Compiling Work around on runtimes |
| Reader's Clinic - EVAL |
| QTIPS - Compiling Protection Code |
| RTP5 and RTP51 |
| Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd) |
RevMedia FKB
| Document | V3I3A8 |
| Title | QTIPS - Compiling Protection Code |
| Keywords | COMPILE CODE PROTECT |
| Text | To see the generated code for the protection ("Compiling Protection Code") create a blank record in the dict of the file to be protected called %PROTECT SRC% Then perform an action which causes the "Compiling Protection Code" message to be displayed AFTER the protection code has been compiled the source will be left in here A careful examination of this code can be used to predict how many fields WITH CONVERSIONS a file can have before SQL can no longer be used on it Failure to compile because the protection code is too large is usually evidenced by a FS251 message (Volume 3 Issue 3 Page 14) |
Page last modified: 08/02/03