Data Dynamics Reports
Royalty-free reporting toolkit based on the Report Definition Language (RDL).
Publié par MESCIUS (formerly GrapeCity)
Distribué par ComponentSource depuis 1996
Data Dynamics Reports integrates into Web and Windows Forms applications and provides a rich API with which to create and modify reports. In addition to the base features provided by RDL, Data Dynamics Reports has added several features including: Master Reports, additional chart types, banded List data region, barcode report item, formatted Text report item, themes and data visualizers. Documents created with Data Dynamics Reports can layout data using a combination of Lists, Tables, Charts, Matrices or Banded Lists in a layout-based report. Reports can be populated with data from an ADO.NET DataSet, .NET Object, SQL Server, Oracle, OLEDB, ODBC, or an XML data source.
Data Dynamics Reports has all of the features found in RDL and has added several enhancements:
Rendering extensions are more than just an export, they render the report using the underlying layout of the report. This means that each report item can be rendered in a way that makes sense for that rendering extension. Rendering extensions available:
Data Dynamics Reports includes several controls that you can ship with your applications:
Data Dynamics Reports is not a replacement for ActiveReports for .NET. The goal behind creating Data Dynamics Reports is to create a reporting product in which users need not write code to create most basic reports.
What are the main differences between Data Dynamics Reports and Active Reports for .NET? Briefly, Data Dynamics Reports supports multiple data sources, data sets, and several different data regions. It also supports the use of VB.NET expressions to set properties. These expressions control the entire report generation process and replace the event handlers fired from within ActiveReports for .NET.
Expressions - With ActiveReports for .NET, if you want to set the color of a TextBox at run time based on its value, you have to write an event handler like the following:
private void detail_Format(object sender, EventArgs e)
{
if ( ( (double) textbox.Value) < 0.0 ) {
textbox.ForeColor = Color.Red;
}
else {
textbox.ForeColor = Color.Black;
}
}
In Data Dynamics Reports you instead use expressions- snippets of inline VB.NET code that when executed return the value desired. The expression to duplicate the event handler earlier would be written like so:
=IIF( Fields!field.Value < 0, “Red”, “Black” )
Multiple Data Sources/Data Sets - Each report can have multiple data sources and data sets associated with it. A data region and its children can only be associated with a single dataset. If multiple data sets are needed within a data region a subreport can still be used to link in the second data set. However, in most cases a data set that contains the join of both sets of data could be used.
Drilldown - Data Dynamics Reports has true drilldown support, that allows report authors to hide data conditionally in the report and expose it when requested. This is done by setting a report item to be hidden and then setting its ToggleItem property to the name of a textbox or image report item in the report.
Data Regions - A data region is a how a set of data is manipulated to be output by various report items (if needed). The List data region outputs itself once for every row of data in the data set or unique set of grouping expressions. The Banded List functions very similar to how a report in ActiveReports for .NET works. The Chart data region contains the same charting technology used in ActiveReports, but it has been updated to work with the Data Dynamics Reports ideas of a data set and expressions.
Nested Data Regions - In ActiveReports for .NET it is possible to add a chart to any section of the report, but that is the limit of nesting a data region. In Data Dynamics Reports data regions can also be added within data regions that accept report tiems, as long as the data is grouped. The ability to nest data regions means that report
authors don’t have to resort to using subreports which incur additional processing overhead that should be avoided if possible. A standard usage is to nest another data region within the List data region when it has detail grouping set. This set up allows the summary data to be output in the outer List while details are output in the inner List. Another usage is to take advantage of the grouping construct of the Matrix data region. This allows the report author to create a trellis display of charts, tables, or lists.
Matrix (Crosstab) - Data Dynamics Reports also features a matrix data region – sometimes called a crosstab or pivot table. This data region consists of a grid that adds columns and rows for distinct sets of field values in the data set. Many products exist for the same premise, to group data in n-ways and look at the data comes out. Each row or column group in a matrix can optionally have a subtotal column/row as well. This works by taking the same expression in the data cell and expanding its scope to include all of the data in that group.
Table - Data Dynamics Reports offers a Table data region which simplifies the positioning and sizing of report items in a grid format. The designer makes it easy to set gridlines on the table as well.
Data Dynamics Reports Frequently Asked Questions
Question: What are the differences between Data Dynamics Reports and ActiveReports for .NET 3.0?
Answer: Data Dynamics Reports targets reporting as a function of business intelligence applications while ActiveReports for .NET focuses on providing the most flexible object model that gives developers the freedom to customize and create complex reports with ease.
Data Dynamics Reports is designed to require less code "behind" the report and instead to use Visual Basic .NET expressions within report item properties to evaluate values. ActiveReports for .NET on the other hand, is a very developer-oriented system that features events for complete run-time customization of the report.
Both Data Dynamics Reports and ActiveReports for .NET include WebForms report preview controls, however ActiveReports also includes an ActiveX-based viewer that renders the report graphically instead of through HTML and CSS. Both products also include Windows Forms report preview controls and end-user designer components. Data Dynamics Reports ships with pre-built applications for report viewing and creation.
Data Dynamics Reports supports different data regions. In ActiveReports for .NET, a report is created in a series of bands, each band displaying its data in certain parts of the report. Data Dynamics Reports supports this data region, called the Banded List, and also supports Table, Chart, Matrix (crosstab), and List data regions.
Features available only in Data Dynamics Reports include:
Features available only in ActiveReports for .NET include:
Special Data Dynamics features in both products include:
Question: What are the differences between Data Dynamics Reports and Microsoft SQL Server Reporting Services 2005?
Answer: Both products implement the Report Definition Language (RDL) 2005 specification but from there the products differ.
Data Dynamics Reports introduces several features not found in SSRS.
Question: What is the Report Definition Language and why do I care that Data Dynamics Reports supports it?
Answer: The Report Definition Language (RDL) sets out both a file format and how elements in a report should be rendered. It also defines a base set of functionality that should be available in a report.
Some of the features required in the RDL 2005 specification include:
Data Dynamics Reports and Microsoft SQL Server Reporting Services are just two products that implement the RDL 2005 specification.
Question: Does Data Dynamics Reports require Microsoft SQL Server Reporting Services?
Answer: No, Data Dynamics Reports does not build on Microsoft SQL Server Reporting Services (SSRS). Data Dynamics Reports is a self-contained reporting library that contains its own report engine, API, viewer, and designer controls. Data Dynamics Reports can read and execute the RDL files produced by SSRS because the files follow the RDL format, but that is the only connection.