| Bugs and PCs - Xlate with Multipart Keys |
| VROOM - Window Processing II |
| Indexing on Xlates |
| Collector Windows |
| QTIPS - Reusing Symbolics in Windows |
| QTIPS - Hiding Symbolic Source Code |
| Catalyst |
| @ATTACK - @Ans |
| QTIPS - Compiling Work around on runtimes |
| QTIPS - Potential Problem When Using @ANS |
| Reader's Clinic - Screen Width |
| Screen Grabber |
| Reader's Clinic - Slow Multivalued Screen Display |
| Utility Diskette # 4 |
RevMedia FKB
| Document | V3I7A7 |
| Title | Reader's Clinic - Slow Multivalued Screen Display |
| Keywords | MULTIVALUE SCREEN XLATE DISPLAY |
| Text | Martin Northey of the Inland Revenue recently queried why certain screens took so long to display up to 40 seconds in some cases! The delay was tracked down to the existence of several ASSOCIATED multivalues incorporating XLATEs to another file The symbolic being used was @ANS = xlate(FILE KEYS FIELD ACTION)<0 @MV> where KEYS was a multivalued key list The purpose of the <0 @MV> was to prevent a problem whereby if the display area was not filled by MULTIVALUES previous values would repeat to fill up the display area It was found that if the above formula were written as @ANS = xlate(FILE KEYS<0 @MV> FIELD ACTION) the screen refreshed 10 times more quickly as only the MULTIVALUES actually required were calculated! (Volume 3 Issue 7 Page 12) |
Page last modified: 31/01/03