>George, and all,
>
>>In 8.0, you can't do something like the following

SELECT sku, stockcolor, SUM(quantity);
>>  FROM Products;
>>  GROUP BY sku;
>>  INTO CURSOR resultset

>because the query involves an aggregate function (SUM) and the stockcolor field is not in the GROUP BY clause. In previous versions you could. The workaround is to issue SET ENGINEBEHAVIOR 70 immediately prior to issuing the query then SET ENGINEBEHAVIOR 80 afterwards.
>
>
>I think the best workarround is to ensure that all fields not included in the group by clause are aggregated fields by including the MAX function for those fields which are not:
>
>
>

SELECT sku, MAX(stockcolor) as Stockcolor, SUM(quantity);
>   FROM Products;
>   GROUP BY sku;
>   INTO CURSOR resultset

>
>
Walter,

I'd have to disagree completely. First, you obscure the intended output. Second, you're messing with working code (If it ain't broke, don't fix it). Third, and most importantly, you're introducing completely unnecessary processing overhead with the function calls.

This was intended to be, as I said originally, an extremely simple sample. In a reply to Jim Booth on this thread, I clarified by using a much more complex, but real world scenario.

Using SET ENGINEBEHAVIOR avoids all three of the above complications.