That's exactly the problem. Group by may not have been working correctly. The results could be correct for one query but incorrect for the next. That's why it was changed. Using SET ENGINEBEHAVIOR 70 will cause the incorrect behavior to continue to be incorrect.
>Thanks again Sergey.
>When writing Group bys in previous versions it always worked fine for me in the past, provided the clause was written correctly.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer