RE: RPG or SQL?

Hi Steve,

Thinking back on your OP, I still come to the same conclusion.  As I recall,
you want only one model returned per account, but that each account may
refer to many models.  The question remains unanswered, how do you want to
decide WHICH model to return for a particular account.  The answer might be
"the most common" model for that account, meaning that model 'xyz' was
ordered by the customer 30 times, versus model 'abc' which they only ordered
once.  Or, perhaps you don't really care WHICH model you return, as long as
its a model that is associated with the account.  Or, perhaps you wish to
see the LAST model ordered by the customer.  Or.......

Each of these scenarios leads to different selection logic, so it's somewhat
inefficient to try to design a solution to this problem when we don't even
know what the problem is....

Can you elaborate on the requirements for this application?

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of steema@xxxxxxxxxxxxx
Sent: Tuesday, May 02, 2006 9:21 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: RPG or SQL?


HI Perhaps I wasn't clear last time I was talking about SQL.
In RPG I would do a Control Break on Acct & Model, then it would show
me as many fields as needed.
In SQL I do this:
SELECT DISTINCT ACCT, mod FROM *libl/mdpwrk WHERE
acct > 12806 ORDER BY ACCT, MOD.

Because there are many acct/mod records but we are interested in only the
one occurance.

But we also want to see other information such as PO # to help
locate the records.

W/ the SQL it seems that I can only do a 'control break' on the exact
fields that will make up the output. in this case, it seems as I need to
write an RPG program for the Control Break feature?

Steve