RDLC vs RDL Revisited

I have searched the archive of this forum, and based on some previous answers have read the followin FAQ

http://www.gotreportviewer.com/

However, even so, I still have a questoin about when to use RDLC vs RDL from the point of view of licensing and load sharing betwee DB and report server.

1. As we all know that SSRS will take a license of SQL Server if the web service is deployed on any other machine other than SQL Server (which is normally the case because no serious DBA will allow IIS apps to be installed on the DB Server). Also, if the SSRS is deployed on NLB cluster then each node of the cluster would need a "SQL Enterprise" license. (which can be very expensive).

2. Co deploying the SSRS with SQL Server is a bad idea because it puts excessive load on the DB+Report Server.

3. Since there is no "load balancing" in SQL all the rendering has to be done by the SSRS service which is running on the DB Server.

Now compare this to RDLC

1. RDLC gives me the same engine as RDL

2. However it has no licensing tags to it.

3. I can deploy ASP.NET report viewer on my web farm and scale it out as much as I like.

4. Extract data from the DB using stored procedures.

So it seems that RDLC solution is cheaper, gives better scale out capabilities and also moves the rendering of reports on the web farm rather than the Report Server.

Why should me or anyone else choose RDL at all?

There seems to be one disadvantage that the data has to fetched programmatically and manually binded (like an ASP.NET app) as RDLC does not provide any feature to connect to data sources. But this is not much when you see the cost and scalability benefits.

regards,

Abhishek.

bump!|||You have some great reasons for using RDLC.

A few off the top-of-my-head advantages for using RDL rather than RDLC.

1. Subscriptions
2. Caching / Snapshots
3. Role Based security
4. "My Reports"
5. Configuration / Definitions stored in Report Catalog DB
6. Additional rendering formats
7. Sharepoint webparts integration

Without a doubt you can implement similar functionality in your application hosting the RDLC, but these are out of the box when you're using the report server.

I have had several clients start out heading down the road of wanting to use RDLC to avoid the licensing fees. In the end, they all ended up using the report server. There's no one size fits all solution and in many cases, RDLC would be a valuable choice.

Hope this helps.|||

Thanks, I also found information on the MSDN site.

http://msdn2.microsoft.com/en-us/library/ms345248.aspx

regards,

Abhishek.

rdlc viewer issues

I've created a few reporting services local (Visual Studio) reports to see
if this is a viable enterprise reporting option. I'm having rather abysmal
experience with the report viewer.
I design my report in the designer and it looks great. I run the
application and view it on the screen and see
- The left edges of text in text boxes is "clipped", as if the text is
running outside the textbox margin or something
- Some textboxes have switched to multiline as if it isn't long enough to
display the contents, but the textbox isn't tall enough for that and what
displays is just gobbledy-gook.
If I switch the view to print layout mode the clipping is still there but
the textboxes now display the entire contents horizontally like they did in
the designer.
In any case, if I print the report from the viewer it comes out pretty much
like it looked in the designer.
So, to recap:
- Left edges of text boxes are clipped in the viewer
- Reports layout like I designed them when in print layout mode but not
otherwise
- Printed reports don't look like they do when viewed on the screen
I must be doing something horribly wrong or have a misunderstanding of the
paradigm, because in my mind this is ridiculous for a reporting tool to
behave this way. I understand the CanGrow property, but it only controls
vertical sizing and in order to preserve my report esthetics I would need it
to grow horizontally.Make sure you report items (Textboxes, Lines, Rectangles, etc) do not
overlap. This usually causes the report to behave oddly in HTML as it
cannot overlap html objects very well. Usually you can avoid
overlapping items by using a table for your data region, instead of the
freeform List. Also, check the padding of your textboxes, and increase
the padding if needed.
Textboxes do not grow horizontally as this is the layout of the report
and is the behavior by design. You should increase the width of your
textboxes to the max size that you can within your report layout for
the data that will be displayed in them. You can set the CanGrow
property to true, which basically allows the renderer to wrap the text
to another line(s), like you said, controlling vertical sizing.
A lot of times, the result you get from viewing the report in the
viewer in HTML will not be exactly the same as when printing or
exporting to PDF or TIFF. The latter are print layout formats, and
will render the reports slightly different, because their media is
paper. For example, if you report has a page footer, in HTML, the
footer will show immediately after last item on the page, even if the
item is in the "middle" of the page, because HTML does not have concept
of "page sizes". If you print it or export to PDF, you will notice
that the renderer places the page footer at the bottom of the paper
page.
Hope this helps you!
Regards,
Thiago Silva, MCAD.NET
On Nov 22, 7:22 am, "Daniel Billingsley"
<DanielBillings...@.newsgroup.nospam> wrote:
> I've created a few reporting services local (Visual Studio) reports to see
> if this is a viable enterprise reporting option. I'm having rather abysmal
> experience with the report viewer.
> I design my report in the designer and it looks great. I run the
> application and view it on the screen and see
> - The left edges of text in text boxes is "clipped", as if the text is
> running outside the textbox margin or something
> - Some textboxes have switched to multiline as if it isn't long enough to
> display the contents, but the textbox isn't tall enough for that and what
> displays is just gobbledy-gook.
> If I switch the view to print layout mode the clipping is still there but
> the textboxes now display the entire contents horizontally like they did in
> the designer.
> In any case, if I print the report from the viewer it comes out pretty much
> like it looked in the designer.
> So, to recap:
> - Left edges of text boxes are clipped in the viewer
> - Reports layout like I designed them when in print layout mode but not
> otherwise
> - Printed reports don't look like they do when viewed on the screen
> I must be doing something horribly wrong or have a misunderstanding of the
> paradigm, because in my mind this is ridiculous for a reporting tool to
> behave this way. I understand the CanGrow property, but it only controls
> vertical sizing and in order to preserve my report esthetics I would need it
> to grow horizontally.|||Well, I have to say I think not handling overlapping items is a ridiculous
limitation - one that surely has the graphics designers in the crowd
laughing their rears off. My use of it is not a list layout issue, it's a
graphic design issue, so using a table doesn't help. What I'm trying to
create is an effect similar to the windows forms GroupBox whereby there's a
box with a border that is interrupted for the "title" of the box.
Additionally, I'd like the title to be surrounded with a border itself.
This is not really all that complex graphically, so I think it's a rather
sever limitation that the rdlc report can't handle it.
Considering that increasing the width of the textbox doesn't really work.
The problem I'm trying to point out is that I can't predict what it will
look like at runtime while in the designer. And even if I put forth the
painful effort of making a change and then having to run the application to
see the results (another completely ridiculous limitation), the problem
still exists that it would look good in the view but when printed look like
I was an idiot because there'd be a bunch of whitespace in the end of the
box (border).
IMPORTANT NOTE - this is all really a problem with textboxes with borders in
general and really doesn't have anything to do with the fact that I am using
it in an overlapping way in this particular case.
I say again, for a report writer not to be able to predict the results, and
for the results to be that different between viewing and printing, is
unacceptable. Period. Yes, I would expect the differences in the way page
footers are handled because there are no "pages" in HTML. Of course it
would work that way. But not that the actual layout of the body of the
report would change so significantly.
I did not appreciate that the default for the viewer was an HTML view. This
seems like another case where the relationship to the SQL RS engine is a
liability.
"tafs7" <tsilva7@.gmail.com> wrote in message
news:1164347626.531755.16330@.l39g2000cwd.googlegroups.com...
> Make sure you report items (Textboxes, Lines, Rectangles, etc) do not
> overlap. This usually causes the report to behave oddly in HTML as it
> cannot overlap html objects very well. Usually you can avoid
> overlapping items by using a table for your data region, instead of the
> freeform List. Also, check the padding of your textboxes, and increase
> the padding if needed.
> Textboxes do not grow horizontally as this is the layout of the report
> and is the behavior by design. You should increase the width of your
> textboxes to the max size that you can within your report layout for
> the data that will be displayed in them. You can set the CanGrow
> property to true, which basically allows the renderer to wrap the text
> to another line(s), like you said, controlling vertical sizing.
> A lot of times, the result you get from viewing the report in the
> viewer in HTML will not be exactly the same as when printing or
> exporting to PDF or TIFF. The latter are print layout formats, and
> will render the reports slightly different, because their media is
> paper. For example, if you report has a page footer, in HTML, the
> footer will show immediately after last item on the page, even if the
> item is in the "middle" of the page, because HTML does not have concept
> of "page sizes". If you print it or export to PDF, you will notice
> that the renderer places the page footer at the bottom of the paper
> page.
> Hope this helps you!
> Regards,
> Thiago Silva, MCAD.NET
>
> On Nov 22, 7:22 am, "Daniel Billingsley"
> <DanielBillings...@.newsgroup.nospam> wrote:
>> I've created a few reporting services local (Visual Studio) reports to
>> see
>> if this is a viable enterprise reporting option. I'm having rather
>> abysmal
>> experience with the report viewer.
>> I design my report in the designer and it looks great. I run the
>> application and view it on the screen and see
>> - The left edges of text in text boxes is "clipped", as if the text is
>> running outside the textbox margin or something
>> - Some textboxes have switched to multiline as if it isn't long enough to
>> display the contents, but the textbox isn't tall enough for that and what
>> displays is just gobbledy-gook.
>> If I switch the view to print layout mode the clipping is still there but
>> the textboxes now display the entire contents horizontally like they did
>> in
>> the designer.
>> In any case, if I print the report from the viewer it comes out pretty
>> much
>> like it looked in the designer.
>> So, to recap:
>> - Left edges of text boxes are clipped in the viewer
>> - Reports layout like I designed them when in print layout mode but not
>> otherwise
>> - Printed reports don't look like they do when viewed on the screen
>> I must be doing something horribly wrong or have a misunderstanding of
>> the
>> paradigm, because in my mind this is ridiculous for a reporting tool to
>> behave this way. I understand the CanGrow property, but it only controls
>> vertical sizing and in order to preserve my report esthetics I would need
>> it
>> to grow horizontally.
>|||Hey, Daniel
Have you tried using a rectangle with borders, instead of a textbox as
the container? I don't think you'll get quite the same effect as the
GroupBox with the title, but at least your rectangle will serve as a
container for other items, and you can have a textbox on the inside of
this rectangle at the top left corner acting as the "title" (note the
"Parent" property in the property page of any textbox placed inside the
rectangle, and you should see the rectangle name)
There is really nothing that prevents you from overlapping items in a
report, however in this version of the product, it unfortunately
doesn't do well rendering overlaps in all renderers. This is mainly a
problem for the HTML rendering extension of the viewer. The same
report, when exported to PDF, will look perfect, though.
In the Visual Studio designer, when you preview a report that contains
overlapped items, you will get a warning in the output window but this
will not prevent you from running the report:
[rsOverlappingReportItems] The textbox 'textbox3' and the rectangle
'rectangle1' overlap. Overlapping report items are not supported in
all renderers.
Build complete -- 0 errors, 1 warnings
As far as the textbox stretching horizontally, it would make no sense
to allow for textboxes to do that because it could inherently stretch
the width of the report body and page width causing the report to print
extra pages just for the extra width, since the printed page size is a
property that is set in the report (e.g. 8.5x11in vs. 11x8.5in -
portrait or landscape letter).
Now, since you're using the RDLC format, I am assuming you have a
custom application that provides a UI to the user for selecting reports
and entering parameters (if required). If that's the case, then your
application is responsible for providing the data as well and then
handing that over to the ReportViewer control for rendering. As such,
there is no way to "preview" your report from the Visual Studio
designer, because it doesn't know where the data is coming from. I
would recommend developing your reports as regular RDL files to begin
with, so you can test on the VS designer. You can even preview it w/
the ReportViewer by right-clicking the report name in the Solution
Explorer and selecting "Run". This will spin off a separate process
with an external windows app hosting the ReportViewer (note that
because this is a windows app, it still won't render the actual HTML
results you'd get from Internet Explorer).
Once you're happy with the results, you can "doctor" your RDL file so
it becomes an RDLC (see http://www.gotreportviewer.com for more
details) that is usable by your custom application.
Hope this helps you.
If you need any references to help you further your skills in SSRS, I
would recommend reading some of the SSRS team blogs for tips:
All about the ReportViewer - http://www.gotreportviewer.com/
Brian Welcker - http://blogs.msdn.com/bwelcker
Chris Hays - http://blogs.msdn.com/ChrisHays/ <= Sleazy Hacks for SSRS
:)
Tudor's blog - http://blogs.msdn.com/tudortr/
Lukasz Pawlowski - http://blogs.msdn.com/lukaszp/
Bob Meyers- http://blogs.msdn.com/bobmeyers
Regards,
Thiago Silva, MCAD.NET
Daniel Billingsley wrote:
> Well, I have to say I think not handling overlapping items is a ridiculous
> limitation - one that surely has the graphics designers in the crowd
> laughing their rears off. My use of it is not a list layout issue, it's a
> graphic design issue, so using a table doesn't help. What I'm trying to
> create is an effect similar to the windows forms GroupBox whereby there's a
> box with a border that is interrupted for the "title" of the box.
> Additionally, I'd like the title to be surrounded with a border itself.
> This is not really all that complex graphically, so I think it's a rather
> sever limitation that the rdlc report can't handle it.
> Considering that increasing the width of the textbox doesn't really work.
> The problem I'm trying to point out is that I can't predict what it will
> look like at runtime while in the designer. And even if I put forth the
> painful effort of making a change and then having to run the application to
> see the results (another completely ridiculous limitation), the problem
> still exists that it would look good in the view but when printed look like
> I was an idiot because there'd be a bunch of whitespace in the end of the
> box (border).
> IMPORTANT NOTE - this is all really a problem with textboxes with borders in
> general and really doesn't have anything to do with the fact that I am using
> it in an overlapping way in this particular case.
> I say again, for a report writer not to be able to predict the results, and
> for the results to be that different between viewing and printing, is
> unacceptable. Period. Yes, I would expect the differences in the way page
> footers are handled because there are no "pages" in HTML. Of course it
> would work that way. But not that the actual layout of the body of the
> report would change so significantly.
> I did not appreciate that the default for the viewer was an HTML view. This
> seems like another case where the relationship to the SQL RS engine is a
> liability.
> "tafs7" <tsilva7@.gmail.com> wrote in message
> news:1164347626.531755.16330@.l39g2000cwd.googlegroups.com...
> >
> > Make sure you report items (Textboxes, Lines, Rectangles, etc) do not
> > overlap. This usually causes the report to behave oddly in HTML as it
> > cannot overlap html objects very well. Usually you can avoid
> > overlapping items by using a table for your data region, instead of the
> > freeform List. Also, check the padding of your textboxes, and increase
> > the padding if needed.
> >
> > Textboxes do not grow horizontally as this is the layout of the report
> > and is the behavior by design. You should increase the width of your
> > textboxes to the max size that you can within your report layout for
> > the data that will be displayed in them. You can set the CanGrow
> > property to true, which basically allows the renderer to wrap the text
> > to another line(s), like you said, controlling vertical sizing.
> >
> > A lot of times, the result you get from viewing the report in the
> > viewer in HTML will not be exactly the same as when printing or
> > exporting to PDF or TIFF. The latter are print layout formats, and
> > will render the reports slightly different, because their media is
> > paper. For example, if you report has a page footer, in HTML, the
> > footer will show immediately after last item on the page, even if the
> > item is in the "middle" of the page, because HTML does not have concept
> > of "page sizes". If you print it or export to PDF, you will notice
> > that the renderer places the page footer at the bottom of the paper
> > page.
> >
> > Hope this helps you!
> >
> > Regards,
> > Thiago Silva, MCAD.NET
> >
> >
> > On Nov 22, 7:22 am, "Daniel Billingsley"
> > <DanielBillings...@.newsgroup.nospam> wrote:
> >> I've created a few reporting services local (Visual Studio) reports to
> >> see
> >> if this is a viable enterprise reporting option. I'm having rather
> >> abysmal
> >> experience with the report viewer.
> >>
> >> I design my report in the designer and it looks great. I run the
> >> application and view it on the screen and see
> >> - The left edges of text in text boxes is "clipped", as if the text is
> >> running outside the textbox margin or something
> >> - Some textboxes have switched to multiline as if it isn't long enough to
> >> display the contents, but the textbox isn't tall enough for that and what
> >> displays is just gobbledy-gook.
> >>
> >> If I switch the view to print layout mode the clipping is still there but
> >> the textboxes now display the entire contents horizontally like they did
> >> in
> >> the designer.
> >>
> >> In any case, if I print the report from the viewer it comes out pretty
> >> much
> >> like it looked in the designer.
> >>
> >> So, to recap:
> >> - Left edges of text boxes are clipped in the viewer
> >> - Reports layout like I designed them when in print layout mode but not
> >> otherwise
> >> - Printed reports don't look like they do when viewed on the screen
> >>
> >> I must be doing something horribly wrong or have a misunderstanding of
> >> the
> >> paradigm, because in my mind this is ridiculous for a reporting tool to
> >> behave this way. I understand the CanGrow property, but it only controls
> >> vertical sizing and in order to preserve my report esthetics I would need
> >> it
> >> to grow horizontally.
> >

rdlc show querystring parameter in page header

I pass in 3 querystring parameters to my web form. The Object Data Sources pick up these parameters

and select the appropriate records.

I want to display one of the querystring parameters in my Page Header, specifically the one for Fiscal Year.

I could return the Fiscal Year in a column from the data source, but the Fiscal Year would not populate if

no records were returned...Therefore, I must get the querystring parameter that was originally passed in...

How do I populate the report control textbox with the value of querystring parameter?

Thanks!

Jim

JIM_LANGDON wrote:

I pass in 3 querystring parameters to my web form. The Object Data Sources pick up these parameters

and select the appropriate records.

I want to display one of the querystring parameters in my Page Header, specifically the one for Fiscal Year.

I could return the Fiscal Year in a column from the data source, but the Fiscal Year would not populate if

no records were returned...Therefore, I must get the querystring parameter that was originally passed in...

How do I populate the report control textbox with the value of querystring parameter?

Thanks!

Jim

Are you using a report generator?

If not, then isn't this is as simple as setting the expression of the textbox to:

=Fields!FiscalYear.Value

|||

I don't know what you mean by "Report Generator"..isn't it SSRS?

I pass in the parameter via the call to the webform that contains the

reportviewer control -- webform.aspx?fy=2007.

The reportviewer control that is bound to the report.rdlc.

The RDLC has several datasources which show up as objectdatasource controls

on the web form. The objectdatasource controls are configured to use the appropriate

datasource method and the parameters are defined to use the querystring and "fy" as

the parameter name.

Doesn't the Fields! collection just have the datasource columns? I tried what you suggested

Fields!fy.Value, since the name in querystring is "fy"...no success.

|||

JIM_LANGDON wrote:

I tried what you suggested

Fields!fy.Value, since the name in querystring is "fy"...no success.

This is probably because you need to specify the dataset on the textbox. Right click the textbox and select properties. In the "containing group or dataset" textbox, you need to either select or enter the dataset that contains 'fy'.

Basically, you can treat a textbox similarly to a table/matrix. It can have a dataset associated with it and you can populate the textbox with any value from the parameters or fields list.

|||

But the querystring does not belong to a "dataset"....so I can't reference it with Fields!fieldname. Hmmm.

|||

Isn't fiscal year one of your fields in a dataset? Aren't you trying to get fiscal year in a textbox?

Why do you want to touch a querystring?

|||

I could return the Fiscal Year in a column from the data source, but the Fiscal Year would not populate if

no records were returned...Therefore, I must get the querystring parameter that was originally passed in...

The goal is to display a specific querystring parameter in the page header of the report.

|||

JIM_LANGDON wrote:

I could return the Fiscal Year in a column from the data source, but the Fiscal Year would not populate if

no records were returned

Yes, and you could conditionally specify what the Fiscal Year should default to if no records are returned.

If you'd like to pursue the querystring path to resolve this, feel free. I'm just somewhat confused with your reasoning.

|||

The Fiscal Year that is passed to the web form is 2006. If no Fiscal Year is passed, it will default to 2007. The records selected are based on the year that is passed in.

If I pass in the year 2006, I want the page header to display "Fiscal Year: 2006" and the body to display "No records found."

It seems clear to me that the querystring is the only place to logically capture the Fiscal Year. Is there another method you had in mind to meet the goal or another way to do things to accomplish the same thing?

|||

JIM_LANGDON wrote:

It seems clear to me that the querystring is the only place to logically capture the Fiscal Year. Is there another method you had in mind to meet the goal or another way to do things to accomplish the same thing?

Maybe I just don't know what you mean by "querystring".

I think everything that you have mentioned so far can be accomplished by using a dataset (as either text or stored procedure).

|||

Sounds like what you have to do is one of the following:

add a new parameter to the report (with no valid values) and set the value of this parameter from the querystring. In your report textbox use Parameters!<your param name>.value to display the value

OR

create a new dataset in your report and load the querystring parameters into it in code, pass this additional dataset to the report

|||

The report page is initiated by a link <a>, html anchor tag.

<a href="report_web_form.aspx?fy=2006">Run This Report</a>

The href property assignment is what I mean by "querystring".

The dataset that is generated uses the 2006 value to determine what

records to select. If no records are returned, you cannot use the dataset to

get the value 2006. I don't see how this can be accomplished using a dataset.

|||

Thanks Adam..

From your first solution how do I "set the value of this parameter from the querystring". Where is that done. Are we talking about an assignment in the page load event of the report web form?

From your second solution how do I "load the querystring parameters into it in code"?

Sorry, I just need a bit more explanation.

|||

OK, here we go. The solution. Thanks to the exhausting yet always productive discussion today.

1. Define a report parameter in the report.rdlc:

Name: FISCAL_YEAR

Data Type: String

"Hidden" checkbox checked.

Default Values: "null" checkbox checked.

2. Place a text box in the page header of the report.rdlc with the value "=parameters!FISCAL_YEAR.Value".

3. Place the following code in the report web form:

Imports Microsoft.Reporting.WebForms

Partical Class reportWebForm

Inherits System.Web.UI.Page

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

Dim _fiscalYearParameter As New ReportParameter("FISCAL_YEAR", "2007")

_fiscalYearParameter.Values(0) = Request.QueryString("fy")

ReportViewer.LocalReport.SetParameters(New ReportParameter() {_fiscalYearParameter})

End Sub

RDLC Reporting Service - setting up query parameters - is this possible?

Hi, I have my RDLC report, called on a ReportViewer, which receives a parameter (id of a column to filter the data), and the report receives this parameter very well, however, I want to use the value of this parameter to a query parameter of the dataset. On VS2005 we can asociate data sets to a report, but not a report parameter to a query parameter...is there any way to make this work?

I've heard that this is not possible using client report and report viewer, as print button. If I use a server report, will I have the print button on my application available?If not, how can I present the report with the print button available?

Thanks a lot!

You must use a server report to use reporting services built in print functionality.

For the parameters, you can programaticallly declare an array of parameters and pass them to the report. The report has a parameter section in the report properties where you can map the parameters. Alternatively, you can use any "parameters" in the creation of your datasets and not pass any parameters to the report.

|||

dr_99:

You must use a server report to use reporting services built in print functionality.

For the parameters, you can programaticallly declare an array of parameters and pass them to the report. The report has a parameter section in the report properties where you can map the parameters. Alternatively, you can use any "parameters" in the creation of your datasets and not pass any parameters to the report.

Yes I'm sure about that, thanks a lot!Only one problem, on IE the print button appears, but on Firefox does not appear, has anyone ideia what can cause this?It is set to visible!Thanks!

RDLC printing/scaling issues?

I am trying to print a .RDLC file programmatically as per the article here: http://msdn2.microsoft.com/en-us/library/ms252091.aspx. The only difference is that I am actually printing to a real printer (HP 1320n).

I am doing this in the context of an ASP.NET web service.

The issues that I am having are that when I execute the web service on my development workstation running IIS, the .RDLC prints to the network laser beautifully; but when I try to run the exact same code on the server (Win2003 SP1), the report prints, but is scaled up by about 125% so that it doesn't fit on the printed page.

This is obviously very frustrating. I have the same driver version installed on both machines, the drivers are configured identically, and the .RDLC file is identical.

Any clues?

Thanks,
Matthew

Are you running RS2005 SP1? I believe some scaling issues were fixed in it.

rdlc parameters error

I have :

Dim params(0)As Microsoft.Reporting.WebForms.ReportParameterparams(0) =New Microsoft.Reporting.WebForms.ReportParameter("aa","47",False)

ReportViewer1.LocalReport.SetParameters(params)

ReportViewer1.ServerReport.Refresh()

but it make error :

An error occurred during local report processing.

Microsoft.Reporting.WebForms.LocalProcessingException was unhandled by user code
Message="An error occurred during local report processing."
Source="Microsoft.ReportViewer.WebForms"
StackTrace:
at Microsoft.Reporting.WebForms.LocalReport.CompileReport()
at Microsoft.Reporting.WebForms.LocalReport.SetParameters(IEnumerable`1 parameters)
at _Default.Page_Load(Object sender, EventArgs e) in E:\Moje dokumenty\Visual Studio 2005\WebSites\VB\AJAXEnabledWebSite5\Default.aspx.vb:line 13
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hello,

Maybe u need to determine the process mode by

ReportViewer1.ProcessingMode = Microsoft.Reporting.WebForms.ProcessingMode.Local

or add to

ReportViewer2.ReportPath = Path Of report & "Inv_DamageVoucher_Template_En"

ReportViewer2.SetParameter("<Perametername>", "<Parameter Value>")

ReportViewer2.Parameters = Microsoft.Samples.ReportingServices.ReportViewer.multiState.False

|||

I use it several times and it works fine the problem with the false parameters try use this

string strTime = System.DateTime.Now.ToShortTimeString();
RptParameters[0] =
 new Microsoft.Reporting.WebForms.ReportParameter("ReportParameterName",Value);
RptParameters[1]=
 new Microsoft.Reporting.WebForms.ReportParameter("ReportParameterName",Value);

http://forums.asp.net/p/1168478/1951923.aspx#1951923

RDLC Object datasource can't get System.Web through webform reportviewer

I am running an RDLC with a object datasource. In the object I try to
access System.Web.Httphandler to get the session, but it is nothing.
The reportviewer running my rdlc from a webform, and it seems as though
there is a setting or something to enable the object datasource access
to the session but I cannot figure it out.
Can someone help?Currently I get this error when it tries to access
System.Web.Httphandler.Current
Microsoft.Reporting.WebForms.AspNetSessionExpiredException|||lotta typos today, I am accessing:
System.Web.HttpContext.Current.Session("PhysicalWebPath")
and Current is Nothing|||This is not too surprising. The web control uses web services. I am not sure
it has a physical web path. What are you trying to determine?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <gfricke@.gmail.com> wrote in message
news:1132681439.261358.193190@.g43g2000cwa.googlegroups.com...
> lotta typos today, I am accessing:
> System.Web.HttpContext.Current.Session("PhysicalWebPath")
> and Current is Nothing
>|||Just trying to grab a session value, so if its a web service that the
web control uses, is there an EnableSession true setting I cause use in
my object datasource like I do in a standard webservice to share the
session?|||Sorry, can't help you there. I have been using the winform control.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <gfricke@.gmail.com> wrote in message
news:1132689249.764262.282850@.f14g2000cwb.googlegroups.com...
> Just trying to grab a session value, so if its a web service that the
> web control uses, is there an EnableSession true setting I cause use in
> my object datasource like I do in a standard webservice to share the
> session?
>|||On a side note, can I see these webservices? Like does it create a
asmx file or something I can connect to in IE for the object
datasources the reportviewer communicates with?|||The webservices are documented and you can use them yourself. Prior to 2005
people would (and still can) roll there own, not using the control. The
previous control (really a sample) used URL integration and so had some
difficulties.
In Books Online look for web services and you will see lots of
documentation.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <gfricke@.gmail.com> wrote in message
news:1132690648.480837.290540@.o13g2000cwo.googlegroups.com...
> On a side note, can I see these webservices? Like does it create a
> asmx file or something I can connect to in IE for the object
> datasources the reportviewer communicates with?
>

RDLC not recognizing DataSet

ASP.NET 2.0 Project
Added
rdlc file
DataSet with DataTable to be populated dynamically at runtime
I cannot set DataSetName in the dropdown -- it does not recognize my
DataSet and I cannot type into it.
If I compile I receive this error for my RDLC
"Error 1 The table 'table1' is in the report body but the report has
no data set. Data regions are not allowed in reports without
datasets."Are you saying that in the "Report Data Sources" window you do not see any
datasets (it actually shows the datatables) in the "Project Data Sources"
dropdown?
Where exactly are you trying to enter this dataset
Do you have an xsd created?
In the datasources window (Which shows when you are looking at a report),
what do you see? And can you create a new datasource from there?
// Andrew
> ASP.NET 2.0 Project
> Added
> rdlc file
> DataSet with DataTable to be populated dynamically at runtime
> I cannot set DataSetName in the dropdown -- it does not recognize my
> DataSet and I cannot type into it.
> If I compile I receive this error for my RDLC
> "Error 1 The table 'table1' is in the report body but the report has
> no data set. Data regions are not allowed in reports without
> datasets."
>

Rdlc LineChart

hi,

Please let me know

I am a new in Rdlc LineChart i want to learn Linechart step by step which site is best for to me.

regards

kumar

You can easily do this read this articles and it was like as normal RDL use these articles for more info

http://www.c-sharpcorner.com/UploadFile/asif.blog/rsweb10109152006235137PM/rsweb101.aspx

http://www.simple-talk.com/sql/learn-sql-server/beginning-sql-server-2005-reporting-services-part-3-the-chart-control/

|||

Hi,

Thanks for your response But i need to create the chart in RDLC not in RDL

But in RDLC creating datatset through the code only and create Report.rdlc in that

above URL guide through the creating dataset through the Object based.

I need to create the dts thorough code.

plz let me it is more urgent to me.

regards

kumar

|||

iif you need to set the data source by code you can check this examplehttp://www.c-sharpcorner.com/UploadFile/justinsaraceno/Main03292006094032AM/Main.aspx

|||

iif you need to set the data source by code you can check this example

http://www.c-sharpcorner.com/UploadFile/justinsaraceno/Main03292006094032AM/Main.aspx

http://www.gotreportviewer.com/.

RDLC Client Report and query parameters and print button

Hi, this is my first post here. I hope to be helpful trying to help and not only asking questions arround here. After I have my report ready I will share here the total experience from top to bottom!But for now, here's the issue:

I'm building a RDLC Repor on my ASP.Net VB web application. I added the .rdlc file to the application and created a table to show lines of data binded from a dataset. The thing is:

- The DataSet expects a parameter @.intNumber, a identifier to get the correct data to display the correct report.

- I'm using ReportViewer to view the report, and by code I've passed a Report Parameter to the *.RDLC report with success, just like this:

Dim parms(0) As ReportParameter
parms(0) = New ReportParameter("intNumber", 37)
ReportViewer1.LocalReport.SetParameters(parms)

The present issue is the following:
I want to use that parameter sent to the report to be sent to the query of the DataSet as parameter to the query to return the data to fill the report. I've heard that this is not possible, just with report server...

Another issue is the print button, also heard that only can appear on report server...no way to display and work on RDLC reports?Very confused right now...these issues are stupid, MS tools should allow these operations, which are not efficient if this is not possibla on RDLC...

In report viewer local mode, your application is loading the DataSet, not the Report Viewer. Therefore you need to supply the parameter when calling your TableAdapter's Fill method.

-Albert

RDLC and Excel - No Grid Lines

Using ASP.NET 2, C#, Web application, we have an rdlc report which will be primarily used to export to an Excel spreadsheet. When we run thw report, then export it, we wind up with a spreadsheet with no gridlines, eg a spreadsheet with invisible cell borders.

Is the a setting or property somewhere which can be changed so that the spreadsheet which opens after the export looks like a standard spreadsheet, that is, with visible cell borders?

Many thanks
Mike Thomas

In the test I just did, setting the BorderStyle to Single on the text boxes I wanted to have borders worked. You should also take a look at http://msdn2.microsoft.com/en-us/library/aa178951(SQL.80).aspx to see how cells are converted. Short and sweet: best, use a table; next best, make sure to align everything.

Larry

|||

Sorry, it's late. I should have also mentioned that every cell in a table and a matrix are textboxes. The BorderStyle is 'none' by default and the BorderColor is 'Black' by default. The properties I mean are those in Visual Studio, not those found through the context menu.

Larry

RDL vs RDLC

My application is a large windows form app that connects to databases via webservice. The client has no ability to get to the SQL Server. Do I even have an option of using Reporting Services, or do I have to use client deployed reports in RDLC files and pass it a dataset? If so, what are the advantages of using SSRS?

I don't have a problem with this method, since it is pretty much identical to what we do with Crystal Reports, but I want to make sure I understand the alternatives.

Thanks

The FAQ section about the ReportViewer controls may be helpful (e.g. #8): http://www.gotreportviewer.com/

-- Robert

RDL to RDLC Dataset Bind Question

We got some existing Reports that are set to RDL files but now they want to be able to create a web user interface so the user can interact through such method. As I am finding out, these reports need to be converted to RDLC so that they can all the proper information so they can be binded. My question is, the datasets are already set (I beleive it's the .rdlc.data files) on the RDL solution project. Now I want transfer those DataSets to my Website project and bind those datasets to my Report Viewer Control. Is that the right approach? Or do we have to re-create the Datasets and then bind? Can I use Web Services to bind to these reports? Thanks for the input and all help is appreciated.

there is no need to do this what you need to do is to just deploythose reports on the reporting server then create web page and addreport viewer control to it to enable the user view the reports youdeveloped you can see this example to know how to do this

http://www.c-sharpcorner.com/UploadFile/asif.blog/DynamicDataGrouping08042006115320AM/DynamicDataGrouping.aspx

http://www.gotreportviewer.com/

rdl or rdlc for custom reports

Are custom reports going to carry on using the rdlc extension. If so is the rdlc extension going to be associated with the reporting project designer. Currently rdlc files only show up the designer and not the data or preview tabs in BIDS.

Paul's documentation blog post refers to rdl rather than rdlc files.

Simon, the final release of SP2 will default to RDL files rather than RDLC files.

Cheers,
Dan

|||

If you don't want to rename your report files to .RDLC for the November CTP, you can type "*.RDL" into the custom reports dialog and hit enter. The report will load just fine... however, any subsequent drilldown actions to other reports will probably default to a .RDLC extension instead of .RDL.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||Exactly, thats what I found :)

RDL and Data

Hi, does anyone know how to (if possible) to decouple the RDL file
from the embedded dataset reference? I know how to do this with the
RDLC file but not the other.The only option is to write a data processing extension. Look up the phrase
in Books Online.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<ross_smith@.csaa.com> wrote in message
news:345d7886-7370-4720-8109-2c79a9ca85fe@.j28g2000hsj.googlegroups.com...
> Hi, does anyone know how to (if possible) to decouple the RDL file
> from the embedded dataset reference? I know how to do this with the
> RDLC file but not the other.|||On Feb 21, 7:43=A0am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> The only option is to write a data processing extension. Look up the phras=e
> in Books Online.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <ross_sm...@.csaa.com> wrote in message
> news:345d7886-7370-4720-8109-2c79a9ca85fe@.j28g2000hsj.googlegroups.com...
>
> > Hi, does anyone know how to (if possible) to decouple the RDL file
> > from the embedded dataset reference? I know how to do this with the
> > RDLC file but not the other.- Hide quoted text -
> - Show quoted text -
Thanks, i will check it out