Yes you do, you won't know which one will be returned without the top 1.

The width of the table.. not the text in the variable!!!

That's almost like a cheap shot, ain't it?

We still can't do squat without the sample data and required output. Do you want help or not???

Generate insert statements

That's why I had the walls painted yellow here... I can just write straight on them without anyone noticing .

Shouldn't be too hard for a DBA .

Nothing wrong with that (unless the design is wrong, but that's another story). The only thing that might be wrong is if you want to keep the meaning of...

Browse the forums, there's another search feature in there.

Go back one step, did you say that all fields will allow nulls???

This still can be optimized a lot... the first 3 subqueries could be turned in a single derived table, then I should probabely read the rest of this monster

Still using the bulldozer approach???

What are the possible range of values for each parameter?

Do you need to have them converted into columns or a batch of rows?

Why not make a 4th table that would keep the kits, and then do the sum based on a kit?

This is still all missing.

- Table definitions

- sample data

- wrong resultset

- expected resultset

Help us help you

Generate insert statements

Also expect to have to...

Maybe you can give him what he wants (or else give him what he needs). Maybe you can give him 2 different reports (assuming those are just flag bits)....

Select the data you need with the group by (without the next 7 columns). Make that a derived table and rejoin back to the base table and then include...