Adam,

Beautiful, thank you.

Yeah, it's just EDB being overly-aggressive in the query compilation phase.  It's making sure that you don't try to do an ORDER BY in a situation where you're not selecting any columns, only expressions and aggregates.  However, it's doing it wrong.  It needs to also look to see if you've specified a GROUP BY, which you have, in which case it should let it go.

I'll have a fix up in the next minor release (not a new build, due to some new stuff).

The workaround is to simply leave that commented-out column in, if possible.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Cool, I get it now: All the columns were computed / generated in the version that gives the error. It is such a rare case it doesn't matter much, but as you say it _should_ work, so brilliant if it can be fixed in a future release.