A good old IBM answer - it depends ... ;^)

For me if this is a one time request - for in house or management use and
then gets tossed or shredded, then STRSQL or iNav SQL Scripts to create the
report and then print it raw without pretty headings, page numbers, etc.

If it is for outside the company or going to be run periodically then I will
put the SQL in a Query Manager Query, use a form, and pass any parms needed.

If it is more complex, the embed the SQL in COBOL to have it select the
records to process, then do what is needed. It can really simplify the
programming on complex selections.

Better than open query file and RPG? Not really. I think it might be easier
to maintain than open query file.

Just my 2 pennies worth.


On Fri, Mar 21, 2008 at 10:18 AM, Tim Gornall <tgornall@xxxxxxxxxx> wrote:

There appears to be much SQL talent on this list, and I'm thinking I may
way behind the times. So here's a "how are you guys doing it" question.
A typical example: A request comes in for a new report. It will require
the user to enter some selection data (let's say from and to dates), then
process a bunch of records within RPG. I'm still using open query files,
record select logic in RPG, etc. Are some of you using SQL to do this, is
it a better way, or just different? Would anyone like to share example
of a clean lean application using SQL?

Thanks, Tim

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].