| Gas Bar |
| VERBatim - V9 |
| @ATTACK - @Rec.Count |
| QTIPS - Replacing GAS.BAR routine during PERFORM "SELECT" |
| A RevTI Techie Replies - Mike Pope - Revelation Technologies (UK) Ltd |
| Background Processing |
| Creating Your Own Background Processes |
| @ATTACK - @Index.Time |
| How Indexes Are Updated |
| 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 |
| Form.List.S |
| QTIPS - Aesthetically Improving RLIST Reports |
| QTIPS - Form Processor |
| QTIPS - Suppressing Initial Form Feed |
| QTIPS - Using RTP29 In Place of V6 |
RevMedia FKB
| Document | V1I7A28 |
| Title | QTIPS - Aesthetically Improving RLIST Reports |
| Keywords | RLIST RTP15 FORM |
| Text | Paul Pickering of PIQ Ltd makes the useful observation that as all print opcodes are routed via RTP15 (REVMEDIA passim) and this keeps track of the line count additional print statements may be introduced into RLIST reports without page control being in any way compromised What this means in practical terms is that if you want to introduce subheadings or special messages into an RLIST report than all you need to do is add a symbolic onto the end of the RLIST STATEMENT WITH the form PRINT STR("=" 70) PRINT MY MESSAGE "C(*)#70" PRINT STR("=" 70) @ANS = "" and RTP15 will do the rest for you Give it a try it is incredibly effective and WITH a little imagination can really improve your RLIST reports The same goes for any routine that goes via the RTP15 processor Try experimenting WITH FORM etc (Volume 1 Issue 7 Page 11) |
Page last modified: 30/01/03