Not that sure what you mean by spoken for.. but...

You can simply hide the whole page footer by turning it off in the report properties. Or if you have something...

hmmm doesn't microsoft use =! (or is it != ) in .net? can't say i've had this problem, but i tend to do my work in the SQL query as...

I Agree with David. Sub reports re-execute the SQL query, no avoiding it. Thats what makes them a little undesirable unless you have good reason to use one.

You may be...

by default RS access is granted to Administrators. You'll need someone who is a member of the Administrators group to grant you Administrator access.

Do this under Site Setting \ Configure...

had another thought... create another version of your procedure, change the data params back to DATETIME

Then after the BEGIN, enter SET DATEFORMAT dmy. eg.

CREATE PROCEDURE dbo.MySProc

AS

BEGIN

SET DATEFORMAT dmy

Hopefully...

we're using RS2000 here which doesn't have a date picker... but I would try this...

I'm hoping that you can set the parameter type in your report as DATETIME but...

I wouldn't use NULL as a valid query parameter, it can get confusing. I'm assuming that when the user selects NULL they mean ALL?

Why not set up your WHERE clause...

I'd say its security related. What credentials are you using to connect to your datasource from the report? Integrated or a generic login account?

We've found its a good idea to...

use the SQL REPLACE function in the query to remove both eg

SELECT REPLACE (REPLACE (MyField, ' ', ''), , '')

so strip out first the double spaces and then whatever...

from memory answer to question 1

You need to remove any prompt text from the parameter and ensure you supply a value to the parameter. This should stop the param displaying.

M

I assume you're using RS2000...

I reckon the problem is the converstion of the datetime param between SQL Server and the report. I'd recommend setting your datetime params in your report...

hmmm pretty sure this is not possible in RS2000, you could do it in Crystal easily ...

Not sure about RS2005 though... i thought i read somewhere that what you...

The difference could just be SQL Server caching the query plan which makes the query execute faster. Parameters entered at run time and the time the plan stays in the...

Why not add the CASE Statement to your Stored Procedure data source and just return it to the report as a field... might wotk better...

you need to delete the file from within Report Manager (RS Web site) as well.

1. Browse to the report on your RS website

2. click on the "Properties" tab

3. Click the...