>
>>Using SET ENGINEBEHAVIOR simply forces you to be aware that there is *potentially* a problem with a given SELECT statement (and that the problem potentially existed in previous versions). That is why I suggested that you turn it on and off, only for certain SELECT statements.
>
>This means, if I am using Group By elsewher, I should add all of the other fields in the select statement except one which have aggregate or sum functions? And this will be better in teh future.
>

It depends on the situation...you wouldn't want to do that if the situation is the same as the one in this thread. If the other fields have non-repeating data, putting them in the GROUP BY will return you more records than you used to get. This may or may not be the correct result :)

>
>>I'll restate it this way: using SET ENGINEBEHAVIOR in VFP8 is not any more dangerous than using that same SELECT statement in another version of VFP.
>>Do you understand the situation?
>>
>Perfect. Makes sense.