Has anyone seen any significant differences using the "RANKED BY HIGHEST 20 TOTAL {FIELD}" command, in WebFOCUS 8? I have. It results in RANKing the LWEST 20 {FIELDs} from high o low... I'm working on it but don't want to go crazy with it...

This message has been edited. Last edited by: Doug,

BTW: It does not malfunction using a simple CAR file fex

TABLE FILE CAR
SUM DCOST
PRINT MODEL
RANKED BY HIGHEST 3 TOTAL DCOST
WHERE COUNTRY EQ 'ENGLAND'
END

This message has been edited. Last edited by: Doug,

BTW: This does not work as is in WF8 but does work quite nicely in WF7:

TABLE FILE WEEKLY_SKU_SUMM
SUM NET_SALES_RETAIL_AMT
RANKED BY HIGHEST 10 NET_SALES_RETAIL_AMT NOPRINT
BY SKU BY SKU_DESC BY DEPARTMENT BY BUYER BY PRICE
WHERE WEEK EQ LAST_WEEK
ON TABLE NOTOTAL
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
. . . 
ENDSTYLE
END

Doug, it would be great if you reproduced this problem using one of the IBI sample files (not CAR if possible), then open a case. This sounds like a major issue.

I appreciate the suggestion. However, I can't dup it with the sample FOCUS files, I tried .

I may need to do a work-around with this via a hold file (which works), at least for now so that production can go on... Probably followed by a case...

quote:

SUM NET_SALES_RETAIL_AMT
RANKED BY HIGHEST 10 NET_SALES_RETAIL_AMT NOPRINT

If you remove the NOPRINT, do the two NET_SALES_RETAIL_AMT columns show matching values?

If not, there is more than one row instance per combination of the sort keys, and you are ranking on detail values of NET_SALES_RETAIL_AMT, rather than the sum; which could explain your difficulty replicating the problem on CAR.