Used the WITH version. Worked fine. Both my ugly version and the 'WITH' version produce 2633 rows in less than a second.

Thanks again.

Thanks for that catch. I'll fix it.

I'm currently stuck on a union query that's lockin up for some reason.

I am enjoying the learning, though.

Again, thanks for the catch!

Part of a larger query that reports on all projects at once.

Since I'm used to Access' limitations on aggregates as subqueries, I'm used to writing these as separate queries and referencing them as views. So that's what I did. Ifeel like...

Ninja,

Thank you so much for your help. I really appreciate it.

Your code seems to miss the interaction between the first "DMAX" and the second. Note...

I was thinking of crosstabs the other day, and ran across an article written by Keith Fletcher on Simple-Talk.com:

http://www.simple-talk.com/content/print.aspx?article=369

That's the printer-friendly version.

He developed a crosstab stored procedure that works...

Jack, after some further research, I found a link to Garth's blog where he did something almost exactly how I needed it done. It is pretty much the same as...

Thank you muchly. some day I'll learn that syntax.

I considered including the DDL script, but decided it would needlesly complicate the question, since it is likely 20 lines long. I got my answer anyway.

I do include DDL scripts...

Not a column. It's a parameter....

Yeah, Todd, I figured that out the hard way today. d'ooohhhh

Perfect, SSChasing Mays, thanks. I'd have beaten on that for hours without you!

I really appreciate the help!

Jim

Possibly good advice, but not the problem. When I changed it to select exactly that field (tblBoMDetail.BoMDetailID) that I needed, it still fails with the same syntax error

Perfect, thanks Ninja.

Since my user interface is Access, I'm gonna use Integer and use the values Access uses (0=true, anything else i.e. -1=false) It's just easier. I'll set a default to avoid...