RDL Project Frequently Asked Questions (FAQ):
1) What is RDL?
RDL is an acronym for Report Definition Language. RDL is an XML based language
created by Microsoft with the goal of promoting interoperability of commercial reporting
products.
2) What is the RDL Project?
Within fyiReporting the software we created surrounding RDL is called the RDL
Project. Look at the Overview, Examples, and Modules links for more details.
3) How is the RDL Project licensed?
The fyiReporting Software RDL Project 3 is released under the terms of the Apache
License Version 2. This license allows you to use the RDL Project 3 libraries and
programs in either open source or commercial applications as long as you credit
fyiReporting Software, LLC.
3) How does fyiReporting's implementation of RDL differ from Microsoft's Reporting
Services implementation?
The goal is for reports that run on Reporting Services to also run on our
implementation. It is not a goal for API compatibility between the products, nor is a full
blown enterprise reporting server part of the RDL project.
4) How complete is the RDL Project's implementation of RDL?
For the first release, the RDL Project won't support three dimensional, bubble or
scatter charting and only HTML, PDF, XML and internal renderers are available.
5) What extensions have been made to the base RDL language?
The main extension has been to allow XML data to be specified in the DataSet
definition. This allows you to try out the example reports without having a database
connection available. There is also a custom extension to allow the HTML file
generated to support sorting of tables within a browser. See the suppliersStyled.rdl
file in the examples.
6) How do I use the .Net control?
To use the .Net control you need to add a reference to the RdlViewer.dll and
RdlEngine.dll in your project. You should then add RdlViewer.dll to your toolbox.
Simply assigning a file name to the SourceFile property will cause your report to load.
Alternatively, assign RDL XML to SourceRdl if you want to programmatically generate
and preview a report. Look at the code in the RdlReader project to see a simple
example exploiting the printing, saving and other capabilities of the control.
7) Where can I find out additional information about the reporting capabilities of RDL?
The RDL specification is the definitive guide to the language. There are a number of
books that explore the reporting capabilities of Microsoft's SQL Server Reporting
Services product (and thus that of RDL). You can search your favorite book site using
'Reporting Services' as the search term to get a list. The online help
gives a detailed look at how to use the RDL Project .
8) How do shared data sources work?
a) Shared data sources are created in the designer using the File/New/Data Source
Reference... menu item. Each file you create is encrypted so that the connection
information is kept confidential. You should use the same pass phrase for all files
created.
b) In a report use the DataSourceReference element when defining the DataSource
(instead of ConnectionProperties).
c) When you open a report with the designer or reader that uses shared data sources
you are prompted for the pass phrase the first time it is needed.
d) When you start RdlDesktop or RdlCmd use the /p argument to provide the pass
phrase needed to decrypt any shared data source files needed. e.g. RdlDesktop
/ppassphrase
9) How to supply data with a report?
An extension to RDL allows you to define data to accompany your report. Go to the
designer Data/Datasets>datasetname... property dialog and the Data panel to define
this data. This feature is extremely useful when you're having problems with a report
defintion and you want to send it to someone (like us) to see what's causing the
problem.
10) Does this software work with Mono?
Yes and no. Version 3 requires .Net 2 and does not currently work with Mono's
support. Version 2 testing with Mono 1.1.13 for Windows shows that the base
reporting engine (RdlEngine.dll) works well. Also the RdlDesktop.exe and
RdlCmd.exe modules work. The RdlDesigner.exe and RdlReader.exe modules do
not work. The RdlViewer.dll when used in RdlTests RdlData.exe works buts has
severe painting problems. In short, if you want to use Mono you are restricted to the
reporting runtime parts of the RDL Project.
1) What is RDL?
RDL is an acronym for Report Definition Language. RDL is an XML based language
created by Microsoft with the goal of promoting interoperability of commercial reporting
products.
2) What is the RDL Project?
Within fyiReporting the software we created surrounding RDL is called the RDL
Project. Look at the Overview, Examples, and Modules links for more details.
3) How is the RDL Project licensed?
The fyiReporting Software RDL Project 3 is released under the terms of the Apache
License Version 2. This license allows you to use the RDL Project 3 libraries and
programs in either open source or commercial applications as long as you credit
fyiReporting Software, LLC.
3) How does fyiReporting's implementation of RDL differ from Microsoft's Reporting
Services implementation?
The goal is for reports that run on Reporting Services to also run on our
implementation. It is not a goal for API compatibility between the products, nor is a full
blown enterprise reporting server part of the RDL project.
4) How complete is the RDL Project's implementation of RDL?
For the first release, the RDL Project won't support three dimensional, bubble or
scatter charting and only HTML, PDF, XML and internal renderers are available.
5) What extensions have been made to the base RDL language?
The main extension has been to allow XML data to be specified in the DataSet
definition. This allows you to try out the example reports without having a database
connection available. There is also a custom extension to allow the HTML file
generated to support sorting of tables within a browser. See the suppliersStyled.rdl
file in the examples.
6) How do I use the .Net control?
To use the .Net control you need to add a reference to the RdlViewer.dll and
RdlEngine.dll in your project. You should then add RdlViewer.dll to your toolbox.
Simply assigning a file name to the SourceFile property will cause your report to load.
Alternatively, assign RDL XML to SourceRdl if you want to programmatically generate
and preview a report. Look at the code in the RdlReader project to see a simple
example exploiting the printing, saving and other capabilities of the control.
7) Where can I find out additional information about the reporting capabilities of RDL?
The RDL specification is the definitive guide to the language. There are a number of
books that explore the reporting capabilities of Microsoft's SQL Server Reporting
Services product (and thus that of RDL). You can search your favorite book site using
'Reporting Services' as the search term to get a list. The online help
gives a detailed look at how to use the RDL Project .
8) How do shared data sources work?
a) Shared data sources are created in the designer using the File/New/Data Source
Reference... menu item. Each file you create is encrypted so that the connection
information is kept confidential. You should use the same pass phrase for all files
created.
b) In a report use the DataSourceReference element when defining the DataSource
(instead of ConnectionProperties).
c) When you open a report with the designer or reader that uses shared data sources
you are prompted for the pass phrase the first time it is needed.
d) When you start RdlDesktop or RdlCmd use the /p argument to provide the pass
phrase needed to decrypt any shared data source files needed. e.g. RdlDesktop
/ppassphrase
9) How to supply data with a report?
An extension to RDL allows you to define data to accompany your report. Go to the
designer Data/Datasets>datasetname... property dialog and the Data panel to define
this data. This feature is extremely useful when you're having problems with a report
defintion and you want to send it to someone (like us) to see what's causing the
problem.
10) Does this software work with Mono?
Yes and no. Version 3 requires .Net 2 and does not currently work with Mono's
support. Version 2 testing with Mono 1.1.13 for Windows shows that the base
reporting engine (RdlEngine.dll) works well. Also the RdlDesktop.exe and
RdlCmd.exe modules work. The RdlDesigner.exe and RdlReader.exe modules do
not work. The RdlViewer.dll when used in RdlTests RdlData.exe works buts has
severe painting problems. In short, if you want to use Mono you are restricted to the
reporting runtime parts of the RDL Project.
 | |  | |  | |  | |  |
Copyright © 2005-2008 fyiReporting Software, LLC. All Rights Reserved.
 | |  | |  | |  | |  |
