Hi George

>Assuming that you've done that, what I'll say is that in all cases it is neither necessary nor advantageous to do anything other than use SET ENGINEBEHAVIOR.

I can understand there is a time when SET ENGINEBEHAVIOR is the easiest answer, but I don't think I'll ever agree that it's ever the correct answer ;).

>
>There's a time to adhere to the standards, and there's a time not to. The trick is knowing (through analysis of the requirements) when and where.
>

Funny, when it comes to spacing in code, you don't seem to agree with that! ;)

>And Walter, adding unnecessary functions, such as MIN(), to an SQL statement unquestionably adds additional processing overhead. There's no question about it.

Absolutely! But I agree with Walter that expecting to get the last record from GROUP BY is uncomfortable.

So, can we not agree that the best answer is to write the code so it's clear what we'll get? SET ENGINEBEHAVIOR TO 7.0 only means results will be what they were before even though the results may be wrong. Further can we not make a recommendation that SET ENGINEBEHAVIOR should be a last resort? As such wouldn't the recommended approach be to do these queries as VFP 8 compatible?