Thanks, Kebbon. Why didn't I think about that?! Welcome to UD, where
stupid things trip me up every day. :-)
Bill
------------------------------------------------------------------------
Kebbon Irwin said the following on 7/24/2009 4:53 AM:
I found that you had to take two steps, first an SSELECT to establish your
order, followed by a LIST (or a sort with the same criteria, but it's
unnecessary in Unidata, even using break-ons and det.supp's).
I was able to get my daily summary of order values with running totals. LIST
ORDERS BREAK.ON ORDER.DATE NUM.ORDERS TOTAL ONE TOTAL ORDER.AMT
RUNNING.TOTAL.AMT DET.SUPP ID.SUPP
Again, many thanks to all who responded.
Cheers,
Kebbon
Date: Thu, 23 Jul 2009 17:01:28 -0700
From: wphask...@advantos.net
To: U2-users@listserver.u2ug.org
Subject: [U2] [Fwd: Re: FW: Running total from UniData dict]
Unfortunately, in UD the @ITEM.COUNT calculates values for LIST only.
Therefore, if you do a SORT the 1st item listed may have an item count
of 5675, the second listed might be 352, etc. Thus, it's very hard to
figure out when you're starting the list in order to initialize the
named common variables.
Bill
------------------------------------------------------------------------
Brian Leach said the following on 7/23/2009 9:38 AM:
[snipped]
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
