It causes you to use astericks in order to make your queries more inefficient :)
Actually, I don't think = in your order by statements is part of ANSI SQL. Think about it - you'd be ordering by TRUE or FALSE, which wouldn't make any sense. I'm actually surprised that Access let's you do it. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, December 04, 2001 4:29 PM Subject: Weird SQL > Hmm, what the hell does the = operator do in the ORDER BY clause? The > query works in Access, fails in SQL Server. > > SELECT tVenTr.*, tVenTrDt.* > FROM tVenTR INNER JOIN tVenTRDt ON tVenTr.lId = tVenTrDt.lVenTrId > WHERE tVenTr.lVenId = 12 > ORDER BY tVenTr.dtDate, tVenTr.lId, (tVenTr.nTranType = > tVenTrDt.nTranType), tVenTrDt.dtDate, tVenTrDt.lId > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
