| Bugs and PCs - Indexing 01 vs 1 |
| Adding Quickdex/Rightdex Indexes Programmatically |
| QTIPS - Descending Order Quickdex/Rightdexes |
| 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 |
| Catalyst |
| @ATTACK - @Ans |
| QTIPS - Compiling Work around on runtimes |
| QTIPS - Potential Problem When Using @ANS |
RevMedia FKB
| Document | V1I1A11 |
| Title | Bugs and PCs - Indexing 01 vs 1 |
| Keywords | INDEXING RIGHTDEX BTREE LOCATE |
| Text | Be aware that as both Rightdex and BTREE rely upon LOCATE BY "AR" the numbers "01" and "1" will locate to the same place in the index and will therefore be confused and one of the values will be lost in the index This means that any the missing key will still be on file but will not be found by index lookups or by popups which use established Rightdexes The best way around this currently is to set up an edit pattern which simply says IF NUM(@ANS) THEN @ANS = @ANS + 0 The act of adding 0 to the entered value forces it to be evaluated as a number and thus strips off any leading zeroes (This does however mean that you cannot have 01 and 1 on file at the same time) Rating Potentially dangerous as apparent data loss (Volume 1 Issue 1 Page 10) |
Page last modified: 30/01/03