Luke,

Thanks for the response. I've never used UNION before, so I'll have to do some studying up on that and then see what I can do.

As for the facilities...

Jeffery,

That seemed to get everything working just fine. No problems getting the SProc created, ran just fine, and it works in the report as well.

Until I break something else, I...

Zipped, and Attached

Alright, I got the parameters taken away, but now I'm back to getting this error message:

TITLE: Microsoft Report Designer

------------------------------

An error occurred while retrieving the parameters in the query.

SqlCommand.DeriveParameters failed because...

There are already more worms that I care to think about. We could all go fishing for months and still have a healthy supply.

Alright, now I have a new problem with it.

Every time I try to run it, it's asking for parameters to be input for Range, EndDate, and HolidayCnt. All of these...

Closed visual studio and reopened it, and now it works...

antonio.collins (8/8/2008)

---

you do realize that if you'd go back to your original code and replace @holidayTbl with @HolidayTbl (as...

Still getting error messages, whether I use my code or yours.

The query was part of an existing report that we have in our ERP system that needs drastic changes made to it. I took the query from there and started...

Lenny (8/8/2008)

---

when you're done, all the code that was in your report (all the DECLAREs, SELECTs, etc) should be in a proc. then, the report should contain only one line:...

I split the two up as I asked about above, just to see what that would give me, and at least the error message changed (though I don't know if...

I took from the replies above that I should just grab the code and chuck it into a SProc, so that's what I did with it (everything in my first...

I get an error report when I stick the code in a SProc.

An error occurred while retrieving the parameters in the query.

SqlCommand.DeriveParameters failed because the SqlCommand.CommandText...