RE: Use for SQL?

There is not. This is part of an older system.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Matt.Haas@xxxxxxxxxxx
Sent: Wednesday, December 20, 2006 4:41 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Use for SQL?

Is there a parent-child relationship defined? If so, you could summarize
the results by the parent account.

Matt 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Phil Kestenbaum
Sent: Wednesday, December 20, 2006 4:30 PM
To: RPG programming on the AS400 / iSeries
Subject: Use for SQL?

HI I am trying to see how to use SQL here.

 

I have to modify a RPG report that prints the customers ranked as top
50. However, in one case, we have many accounts that are actually a
franchise of the same parent company and these appear many times in this
top 50, let us call them Burger-King. They would like to group the
Burger-King accounts so that only one Burger-King will appear on the
report w/ the aggregate totals. For the sake of this report, it doesn't
matter which account number is listed for the total Burger-Kings.

 

There are several steps involved in arriving at the final list, incl.
work files.

 

If it could be hard-coded, to look for all the Burger-Kings that would
be easy but we want to be able to take any account that appears in the
ranking more than once to aggregate it.

 

For timeliness, it seems to me that if I can deal w/ the final file
right prior to printing the report and make the adjustment there that
would be the preferred method. 

 

Can the SQL be able to discern where it has a number of Burger-Kings and
aggregate them?

 

Thank you,

 

Phil 


This message contains information proprietary to our company. It is
intended to be read only by the individual or entity named above or
their designee.
Any distribution of this message or the information contained herein
without written permission from our company is strictly prohibited. If
the reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original message.