7 Answers, 1 is accepted
0
Accepted
Hi Thaer,
The information you've provided is insufficient for us to determine the problem. Please test what is the rendering time when previewing in designer, when showing the report in Web ReportViewer and provide more info on how do you load the report.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
The information you've provided is insufficient for us to determine the problem. Please test what is the rendering time when previewing in designer, when showing the report in Web ReportViewer and provide more info on how do you load the report.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Thaer
Top achievements
Rank 1
answered on 08 Nov 2008, 07:28 AM
when I calling the report is loading the data to be presented and it takes a long time to show the data in Report body with the Picture Generating Report 2 or more
Minutes
0
Hi Thaer,
It is still not clear how do you load the report in the viewer and whether it loads ok in design time and web ReportViewer - can you please answer the questions from our previous post. We also noticed that your last Telerik Reporting download is for Q1 2007, which is almost 2 years old now. Please download the latest official version Q3 2008 and let us know of the outcome.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
It is still not clear how do you load the report in the viewer and whether it loads ok in design time and web ReportViewer - can you please answer the questions from our previous post. We also noticed that your last Telerik Reporting download is for Q1 2007, which is almost 2 years old now. Please download the latest official version Q3 2008 and let us know of the outcome.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Thaer
Top achievements
Rank 1
answered on 17 Nov 2008, 08:53 AM
Fraser is to Sath not clear
I identified the source of the data from the DataTabel be completed before I determined the source of the report
and then Give me the report and the establishment of inter continue to exist, sometimes two or more Minu
I identified the source of the data from the DataTabel be completed before I determined the source of the report
and then Give me the report and the establishment of inter continue to exist, sometimes two or more Minu
0
Hi Thaer,
We have problems understanding your last post - do you still need our help? You do not provide answers to our previous questions, so we're afraid that unless you do, we would not be able to help you any further.
Regards,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
We have problems understanding your last post - do you still need our help? You do not provide answers to our previous questions, so we're afraid that unless you do, we would not be able to help you any further.
Regards,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Thaer
Top achievements
Rank 1
answered on 22 Nov 2008, 06:58 AM
What is it that you do not understand, I offer you my problem, quite clearly, there is no ambiguity in the definition of the problems are clear, sir
Start I Identify The Data to the report by DataTabel and the Report Is Take The Data but later adopted in its Show the Data in the Report , what is the problems is not clear ?
How can I resolve the delay in the presentation of data ?
Start I Identify The Data to the report by DataTabel and the Report Is Take The Data but later adopted in its Show the Data in the Report , what is the problems is not clear ?
How can I resolve the delay in the presentation of data ?
0
Hi Thaer,
Reasons for a report generation to be slow is usually due when Telerik Reporting rendering engine has to perform some calculations, expression evaluations, filtering, HTML generation, and/or other tasks to produce a report. The more complex the report, the more time it will take to get it rendered.
The speed of processing and rendering a report depends on several different reasons, any of which can be the culprits for slow report generation:
Kind regards,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Reasons for a report generation to be slow is usually due when Telerik Reporting rendering engine has to perform some calculations, expression evaluations, filtering, HTML generation, and/or other tasks to produce a report. The more complex the report, the more time it will take to get it rendered.
The speed of processing and rendering a report depends on several different reasons, any of which can be the culprits for slow report generation:
- many report items - report items are
bound to data and are then rendered. If there are many report items on
the report, its generation may take a while.
Solution: Move the separate logical parts of your report into SubReports, which are then combined in one main report. Each SubReport will render on its own and that will decrease the matrix complexity a lot. Try not to put many report items into a single DetailSection. Instead -- divide the report logically into parts and place them in separate subreports. In this manner you will also be able to "assemble" many different kinds of reports later on, once you have created the "building blocks", i.e. the SubReports.
- report layout with misaligned items -
Performance strongly depends on the report layout and the data
displayed, especially when HTML reports are concerned. The HTML
rendering engine creates a complex matrix taking into account every
item's coordinates and size, and then creates an HTML table with many
table cells and rows, some of which are used merely as "spacers". This
way the item's exact locations and sizes are preserved, but with the
cost of many calculations. When a report has tons of items, which are
not vertically and horizontally aligned, the resulting HTML table is
gigantic.
Solution: align your items horizontally and vertically relative to each other. While in TIFF and PDF formats the rendering locations and sizes do not relate to performance, in HTML this is critical. The more items are aligned horizontally and vertically -- the less dummy spacers rows and cells will be created by the HTML rendering engine;
- using the Items.Find method - slow report rendering may be experienced if you use Items.Find to locate your items.
Solution: Telerik Reporting offers a reference to the items in the report, so using Items.Find to locate items is not necessary. For example, instead of writing:
TelItem = Report.Items.Find("txtQuotefor", True)
you can directly refer to the appropriate field and save all that time taken in searching:
TelItem = Me.txtQuotefor
- large amount of data - if your report(s) display large amounts of data, it may take a long time for the data to be retrieved from the database.
Solution: There is not much we can do in this case, other than trying the solution in #1 above. If SubReports do not help, try splitting the report in several simplified reports.
- complicated binding expressions (especially with many report items) require time to be evaluated and they can also lead to slowness;
Solution: Try simplifying the report.
- lots of nested reports - subreports require additional data filtering on the application side;
Solution: Try simplifying the report.
- lots of Chart items -
the charts on a report are rendered once, on report generation. The
generation may slow down if depending on the complexity of the charts
and how many times they repeat (ex. per detail).
Solution: Try simplifying the report.
- Detailed information on your reports
- Your slow report(s)
- The data source you're binding to.
Kind regards,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.