|
Jay Myrick wrote: >You would have an SQL of Select count(*) >from LIBRARY/FILENAME ORDER BY A, B >,C. The SQl statment will be different based >upon if you need to join files and select out >records with the where clause, but you get >the point. Once you have the total records >divide it with lines per page. This approach is >dynamic when the lines per page change. >No second pass stuff or complicated APIs. >Just my humble opinion. We sort of hashed this out a bit earlier. This is great for a simple report where 1 input record = 1 output record. For slightly more complex reports where 1 input record = variable output records this is not as feasible. Imagine a sales report where I read a customer master and list each invoice sold that customer for that period. I could write a second SQL statement to get the total number of invoices, but then I'd have to factor in the number of "invoice headings..." Then there's always new pages for each sales person to throw the count off. Buck Calabro Aptis; Albany, NY "We are what we repeatedly do. Excellence, then, is not an act, but a habit." --Aristotle Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL +--- | 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.