Reporting Services Question using SQL Server 2005

Hi Everybody,

I have created a stored procedure that I am using to pull data into a Reporting Services report created using a database in SQL Server 2005.  I have created the Report.rdl but when I try to run the report with the parameters LocationID put into the box, I get a message that the @LocationID parameter was not supplied.  What is causing this error?  The report has been setup with the parameters correctly.  I am entering the location ID and selecting View Report, an error message appears saying the parameter @LocationID was not supplied.

What do I need to do?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Topic Added:  SSRS SQL Reporting Svc

Topic Advisor
Are you building the report in Report Builder or BIDS?
jjc9809Author Commented:
I am creating a report not using the wizard.  Report Builder is used though.

What is BIDS?

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

OK BIDS is Business Intelligence Development Studio, which is a subset of Microsoft Visual Studio. It works differently to Report Builder.

OK, so Report Builder is really a cut down version of BIDS. You'll need to edit your report in Report Builder, open it up, check the parameter LocationID, is the data type OK? Is the value of the parameter being used in the where clause of your query?

Does your query run without a where clause?
Does the query run with a hard coded value in the where clause?

Is the spelling ( case sensitive) of your @LocationID the same as the spelling in the where clause?

See what you can find, let's us know.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jjc9809Author Commented:

I am working in the Business Intelligence Studio inside Visual Studio 2005.
The datatype for @LocationID is string in the rdl.  I do not have a copy of my stored proc here at home.  I will look Monday and see what the datatype is that the Stored Proc has.  I did not write the complete stored proc, I copied the sp and gutted parts and added a select I needed to pull the Transfer Date.  I believe the stored proc had a parameter @LocationID set up as Integer.  If this is the case that explains trying to load a string lnto an integer type
is causing the error.  The names may not be consistent either.  I will look on Monday.

Hi jjc, did you fix it?

What was the trick in the end? That got you going?

I am just interested,  to get my reading and interpretation of these questions better.


It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.