| SecureUser |
| VERBatim - V25 |
| @ATTACK - @Files.System |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| REVMEDIA Revisted |
| 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) |
| VERBatim - V16 |
| @ATTACK - @Int.Const |
| @ATTACK - @Move.Keys |
| @ATTACK - @Priority.Int |
| @ATTACK - @Macro.Mode |
| Uncommon Knowledge - WC_Unkeys% |
| Utility Diskette # 3 - Part I |
| Utility Diskette # 4 |
RevMedia FKB
| Document | V4I3A2 |
| Title | Readers Clinic - Quickly Coping with \ |
| Keywords | QUERY \ VALIDATION PATTERN |
| Text | Isaac Afrangui writes "In 2 01 if the slash was entered the system would bypass the validation pattern program assigned to the prompt However in 2 11 the validation pattern program is executed then the query window comes up I don't want to rewrite the code Any suggestions?" Alan Humphrey explains "the change was made so developers could trap the \ and prevent the query window" A simple fix is to make "\" the first edit pattern on your prompt This then automatically passes doesn't run other edit PATTERNS pattern and will invoke Query (Volume 4 Issue 3 Page 6) |
Page last modified: 08/02/03