|
On Tue, 20 Jun 2000, Jim Langston wrote: > I have a report to generate that has > quite a bit of text on it. A whole paragraph, basically... I recently created a report that listed individual transactions with error codes on the same line. There were many possible errors which would prevent a transaction from posting, and the user wanted a code next to each transaction rather than a detailed explanation. This saved space on the report, but required a footnote at the bottom of the report detailing each possible error. I created a compile time array with each element being 80 char long. I then typed the entire listing of error codes & messages at the bottom (after the O specs) including blank lines. When the report ran, I stepped through the array printing out each line of the array checking for overflow as I went. This printed out the entire list of errors with page breaks. craig +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.