Re: Should I be using SQL?

Tim,

I, too, am way behind the curve on SQL. But I have found it great for doing the kinds of things you mentioned. Depending upon the requirements, one can use either static or dynamic (Prepare-d) SQL. It is, for me, especially great when the selection criteria vary (dynamic) or I need to pull in a group of records that are spread throughout the table.
There is a very good Redbook on the subject: "Modernizing iSeries Application Data Access" (SG24-5393).
* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Tim Gornall wrote:

There appears to be much SQL talent on this list, and I'm thinking I may be
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 code
of a clean lean application using SQL?
Thanks, Tim