Re: QMQRY QQRYSRC issues group by and order by

[CRPence <CRPbottle@xxxxxxxxx>]

  The given SQL appears as though it may be written with the intent to 
effect a report rather than a set.  It would seem that the GROUP BY 
feature of SQL, which is used to obtain a summarized set, is being used 
instead to represent\reflect the effective BREAK ON CHANGED VALUE 
feature of the Query/400 report writer.  That "Report Break" feature of 
Query/400 is *not* the equivalent of a GROUP BY in SQL.  What is needed 
for the QM Query, is to apply a QM FORM that produces an equivalent of 
the /Report Break/ feature that is found in the Qry/400 report writer. 
In both cases the query is a detail [not summary\summarized] set of data 
that is input to the report writer; the report writer summarizes at the 
/breaks/ on the changing values in the [collated] detail rows.

Regards, Chuck

Frances Denoncourt wrote:
> As many of you suggested earlier, I am trying to switch from
> query/400  to Query Management queries.
>  <<SNIP>>
>  
> My source is (I tried using Select * which didn't work either):
>  SELECT RPPRCL, RPYEAR, RPBTCH, RPNAME, RPREFA, RPCHCK, RPAPYR 
>  FROM TXOVRPP 
>  WHERE RPNAME =  &NAME  OR  RPREFA > &NEGAMT AND RPREFA < &POSAMT
>                         OR  RPPRCL = 'B018034101' 
>  GROUP BY RPPRCL 
>  ORDER BY RPPRCL 
>  <<SNIP>> SQL0122 "Column RPYEAR or expression in SELECT list not valid"