Report Parameter As CheckBox

Hello Sir,
I m working on Microsoft SQL reporting service tool 2005.
I want to know how can display a checkbox on report parameter form
which is automatilcally build by reporting service tool.
Means i want parameter field as checkbox.
I have a query :
select name from employeesTbl
where Sex = @.ParameterValue
User select designation from multiple CheckBox.
and i think remeber i want to know also that user select only one
checkbox at a time.
There may be number of checkboxes for this.
e.g : Male,Female,OtherOn Jun 21, 2:34 am, Dheeraj <dheeraj.dhiman.daffo...@.gmail.com> wrote:
> Hello Sir,
> I m working on Microsoft SQL reporting service tool 2005.
> I want to know how can display a checkbox on report parameter form
> which is automatilcally build by reporting service tool.
> Means i want parameter field as checkbox.
> I have a query :
> select name from employeesTbl
> where Sex = @.ParameterValue
> User select designation from multiple CheckBox.
> and i think remeber i want to know also that user select only one
> checkbox at a time.
> There may be number of checkboxes for this.
> e.g : Male,Female,Other
If I'm understanding you correctly, you will only be able to use a
checkbox as part of a multi-select parameter. Is there a particular
reason why you can't use the standard drop-down list for the parameter
selections?
Enrique Martinez
Sr. Software Consultant

Report parameter - date format

I have developed few reports using reporting services (service pack 2), but
still facing some problem in the date parameter and would look for help /
share here. Thanks advance!
1) How RS treat the date format?
YYYY-MM-DD (the data is correct when i use this format)
DD/MM/YYYY
MM/DD/YYYY
What is the purpose to define the date parameter as "MM/DD/YYYY" from the
"Expression" windows?
Any way to limit the input date format or any method to convert the format
to YYYY-MM-DD if user really input the format as DD/MM/YYYY or MM/DD/YYYY?
2) Anyone know how to use date time picker in RS, or possible to use it? I
believe if RS could use the date time picker, I don't need to worry the
parameter formatHi,
have a look at this article:
http://www.databasejournal.com/features/mssql/article.php/2197931
You'll find the way to solve your problem (I had the same problem and by
converting the date with the CONVERT function in my SQL query I managed to
solve it).
If you have some time could you take a look at my post (just after yours),
maybe you have the solution.
Thanks,
--
JB
"Franklin" wrote:
> I have developed few reports using reporting services (service pack 2), but
> still facing some problem in the date parameter and would look for help /
> share here. Thanks advance!
> 1) How RS treat the date format?
> YYYY-MM-DD (the data is correct when i use this format)
> DD/MM/YYYY
> MM/DD/YYYY
> What is the purpose to define the date parameter as "MM/DD/YYYY" from the
> "Expression" windows?
> Any way to limit the input date format or any method to convert the format
> to YYYY-MM-DD if user really input the format as DD/MM/YYYY or MM/DD/YYYY?
> 2) Anyone know how to use date time picker in RS, or possible to use it? I
> believe if RS could use the date time picker, I don't need to worry the
> parameter format
>sql

Report not rending via web service

I'm somewhat new to reporting services and have used a web service call to
render my reports in my asp.net applications in the past. All the reports
thus far have been Excel, and I've used the same method for calling these
reports from some sample code I found online. This has worked great up till
now.
I have a report I want to render in PDF. I've plugged in the correct values
in my code and the browser will try and download the PDF but returns a "File
is damaged and could not be displayed". I tried rending in Excel and I get
"This file is not in a recognizable format". I've compared my code to past
projects and everything looks good. The only difference with this report is
I used a list control with textboxes instead of a table which I've used on
all past reports. If anyone has a suggestion on what causes these error
message, please reply. Thanks.I figured it out. There was a <httpModules> tag in my web.config that was
causing this problem. I built another project to call my report with a
"clean" web.config and it works fine.
"jweesies" wrote:
> I'm somewhat new to reporting services and have used a web service call to
> render my reports in my asp.net applications in the past. All the reports
> thus far have been Excel, and I've used the same method for calling these
> reports from some sample code I found online. This has worked great up till
> now.
> I have a report I want to render in PDF. I've plugged in the correct values
> in my code and the browser will try and download the PDF but returns a "File
> is damaged and could not be displayed". I tried rending in Excel and I get
> "This file is not in a recognizable format". I've compared my code to past
> projects and everything looks good. The only difference with this report is
> I used a list control with textboxes instead of a table which I've used on
> all past reports. If anyone has a suggestion on what causes these error
> message, please reply. Thanks.

Report Model

Hi there
Has anyone used the new report model in Reporting Service 2005 and
notice d the glaring bugs that are very obvious and make the Report
Model itself a non starter for using.
I just wonder if MS are aware of the bugs which make the product look
unfinished.
Thanks
Gregor SuttieWould you like to perhaps name something specific, Greg? I've noticed a few
things, but not necessarily show-stoppers.
"greg" wrote:
> Hi there
> Has anyone used the new report model in Reporting Service 2005 and
> notice d the glaring bugs that are very obvious and make the Report
> Model itself a non starter for using.
> I just wonder if MS are aware of the bugs which make the product look
> unfinished.
> Thanks
> Gregor Suttie
>|||Can you elaborate on these "bugs?"
I have not begun using SSRS2005 but have not seen much mention of
glaring bugs in other posts.

Report in Report Manager (server) does not look the same way that it looks in the Visual Studio

I am using SSRS 2005 and my server is a Microsoft Windows Server 2003 Enterprise Edition Service Pack 1.

Most of the differences between VS and Report Manager are formatting differences. Borders won't show up, scrolling does not work etc. Is there something i need to upgrade on the server.

Last thing but not the least. Everytime i change something in regards to the parameters i need to delete the report from the report manager and deploy in order for the change to appear on the Report Manager. Is there a fix for this?

Could somebody please help me with these?

1. differences in rendering between design-time and run-time -- the renderer used in Report Designer is quite different than the renderer used in Report Manager. The Designer renderer is GDI-based, whereas the Report Manager renderer is HTML-based. There are many differences between these renderers, including handling of overlapping items, borders, and pagination.

2. changes to parameters made at design-time require deletion and republishing -- this is an artifact of our "server wins" philosophy. Since you can change parameter characteristics in the Report Server after a report has been published 9and therefore which may conflict with the characteristics stored in the RDL), it is indeterminate which version of the parameters a user expects to be persisted -- do you expect customizations made after publishing to dominate, or does republishing dominate? We chose to go with the server's version of parameters. Note that if we chose the other way, you would lose server-based parameter customizations everytime you republished an RDL. Admittedly it it would be nice to give users control over this, like with an RDL-based design-time option to choose which parameter collection dominates, or a publish-time option so you could choose one or the other at publish time.

|||You mean there is no way i can reproduce my params changes in the report manager with out deleting the report itself. Everytime i do that it deletes all the subscriptions on my report. Isn't there any work around?|||

Go ahead and republish the RDL, but don't bother making changes to the parameter properties in Report Designer -- just make them directly in the Report Manager or Management Studio UI.

If you need to change the # or name of the parameters, that will have to be done in Report Designer.

Report in Report Manager (server) does not look the same way that it looks in the Visual Stu

I am using SSRS 2005 and my server is a Microsoft Windows Server 2003 Enterprise Edition Service Pack 1.

Most of the differences between VS and Report Manager are formatting differences. Borders won't show up, scrolling does not work etc. Is there something i need to upgrade on the server.

Last thing but not the least. Everytime i change something in regards to the parameters i need to delete the report from the report manager and deploy in order for the change to appear on the Report Manager. Is there a fix for this?

Could somebody please help me with these?

1. differences in rendering between design-time and run-time -- the renderer used in Report Designer is quite different than the renderer used in Report Manager. The Designer renderer is GDI-based, whereas the Report Manager renderer is HTML-based. There are many differences between these renderers, including handling of overlapping items, borders, and pagination.

2. changes to parameters made at design-time require deletion and republishing -- this is an artifact of our "server wins" philosophy. Since you can change parameter characteristics in the Report Server after a report has been published 9and therefore which may conflict with the characteristics stored in the RDL), it is indeterminate which version of the parameters a user expects to be persisted -- do you expect customizations made after publishing to dominate, or does republishing dominate? We chose to go with the server's version of parameters. Note that if we chose the other way, you would lose server-based parameter customizations everytime you republished an RDL. Admittedly it it would be nice to give users control over this, like with an RDL-based design-time option to choose which parameter collection dominates, or a publish-time option so you could choose one or the other at publish time.

|||You mean there is no way i can reproduce my params changes in the report manager with out deleting the report itself. Everytime i do that it deletes all the subscriptions on my report. Isn't there any work around?|||

Go ahead and republish the RDL, but don't bother making changes to the parameter properties in Report Designer -- just make them directly in the Report Manager or Management Studio UI.

If you need to change the # or name of the parameters, that will have to be done in Report Designer.

Report History in SQL Reporting Service

Hi,

I am using SQL Server 2005 Reporting service. I am working on a report. I have made several subscriptions for it. Report runs according to subscription. SQL Server Reporting service also offers functionality to save report histories. Now how can I configure it so that whenever report runs according to its subscription, a history should be automatically saved?

If in case it is not possible by some automatic process then is there any way to set multiple schedules for history of the single report like multiple subscriptions can be set for single report.

Waiting for your response. Thanks in advance.

Regards,
Sulman.

Under the History Properties of the report, you need to select the option to:
Store all report execution snapshots in history.

There are also other options to indicate how many snapshots you want to keep, as well as creating snapshots on a regular schedule.|||Thanx, J Quick

Yes there is an option in Hisotry properties "Store all report execution snapshots in history". But let me clear how it works.

On the Execution property page there are two option.
1. "Render this report with the most recent data"
This option means that whenever the report will be executed, it will get fresh data from database by making query on it.
2. "Render this report from an execution snapshot"
This option means that an execution snapshot of report will be saved either once when the Apply button is pressed or it will keep on updating depending upon schedule. But at one time there will be only one execution snapsho. And whenever the report will be executed, it will be rendered from that execution snapshot and not from the fresh data of database.

Now i come to History property mentioned above to "Store all report execution snapshots in history". It will work only when the execution property of report is set to "Render this report from an execution snapshot". And if execution snapshot is scheduled to be updated then each time the execution snapshot will update it will also be saved in history as history snapshot. So for this history property to work, we have to sacrifice the updated and fresh data. But in my case, i have to get fresh data every time and also i want to save the history of that executed report. Try to think on this line.

Anyhow i appreciate your effort. Thanx again.

Sulman.
|||

>> "It will work only when the execution property of report is set to "Render this report from an execution snapshot".

I don't think the statement above is correct, but I could be wrong since it has been some time since I tried it.

As I recall, the options to "Render this report with the most recent data" and "Store all report execution snapshots in history" are on different property pages and aren't mutually exclusive.

Report Header and Report Footer

Hi,
Does Report Header and Report Footer exist in Reporting service.
This in similar to Page header and Footer except that report header comes
only in first page and report footer in last page.
And Can I include a rdl file that has parameters in header or footer section
Thanks
KiranVersion 1.0 doesn't have a designated header and footer elements. Instead,
you add your report header and footer section at the beginning and the end
respectively of the report body section.
Not sure what you mean by the second question.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Kiran" <Kiran@.nospam.net> wrote in message
news:OJmN0vn5EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Does Report Header and Report Footer exist in Reporting service.
> This in similar to Page header and Footer except that report header comes
> only in first page and report footer in last page.
> And Can I include a rdl file that has parameters in header or footer
> section
> Thanks
> Kiran
>|||Kiran,
I don't think there is any thing equivalent to #include (or @.import) in
RDL.
However, you can write VBA code which could generate what you need. I
suppose the VBA could even open up another RDL file, and insert its contents
into your report.
You might also consider just using a subreport to achieve this.
Cheers,
Daniel Williams
"Kiran" <Kiran@.nospam.net> wrote in message
news:OJmN0vn5EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi,
> Does Report Header and Report Footer exist in Reporting service.
> This in similar to Page header and Footer except that report header comes
> only in first page and report footer in last page.
> And Can I include a rdl file that has parameters in header or footer
> section
> Thanks
> Kiran
>