Again, the original query produces a list of "programs" that a "player" and or "member" from a particular family are eligible to register for. The result set needs to exclude...

I would probably do it by using a Calendar table. There are a bunch of articles around here this one: http://sqlserver2000.databases.aspfaq.com/why-should-i-consider-using-an-auxiliary-calendar-table.html

You might have to add the column for Nth...

I would run the inserts one at a time and see if they throw errors. Either that or put in some dummy print statements to see which insert/select statement...

Here is the report... Hopefully my table/field names match yours. If not, I can share the table scripts too.

Just realized... I'm using 2012, so I may have to redo...

I think I sorted it out. The problem is that it requires a Calendar table/ table valued function in order to work (because you have to have all the...

One way is to just add a Page Header to your report and put the textbox in it.

So using T-SQL isn't an option, because you're using SSRS?

If you can use T-SQL, something like this should work:

SELECT HeatNo, MAX(Frame) AS MaxFrame, MAX(Window) AS MaxWindow

FROM (

SELECT 1 AS...

dates are numbers, so change the formatting in the textbox properties.

Thanks. That's what I thought, but wanted to make sure I wasn't missing something.

If you're brand new to SSRS, Brian Larson's book is pretty good. Wordy, but he walks you through pretty much every step. His book covers 2008 (not R2, which...

Check out this article [/url].

It shows one of the reasons to have a Calendar table. It makes a job like the one you are attempting really easy.

The problem you...

Any chance you can post the create table scripts for the 3 tables? (Are these part of an external system? the table and field names are mind boggling!)

I guess you don't have to build stored procedures, but it makes things a lot easier.

Any chance you could post some dummy data, so we can see what...

The query you posted had me confused. Once I took a step backward and slapped up a totally fake dataset, this was a snap. I created a bar...

Yes, I admit a CROSS JOIN would kill performance, but I would definitely filter first and then create the smallest cross join possible.

Glad you got it sorted.