Hi damian,
Thank you for the interest in our product. Now on to your questions:
-
Telerik Reporting supports all the standard .NET data source objects. You can specify a data source at runtime.
- Telerik Reporting does have a Chart report item. The Chart has its own separate data source set in the event handler of its NeedDataSource event, so that should be entirely possible. A demonstration of this can be seen in the ProductLineSales sample report that is installed with Telerik Reporting.
- While not automatically, parameters can be passed, but that depends on the developer, i.e. he can pass any URL parameters, read them in the Page_Load method and then pass them down to the report by using Report Parameters.
- Telerik Reporting is an embedded reporting engine and as such can be used in any .NET application, be it Windows Forms, ASP.NET or a console application. You do not need to install Telerik Reporting on a Web Server, you only need to have the required assemblies in the Bin folder of the ASP.NET application using Telerik Reporting. Same applies for Windows Forms applications.
- Since Telerik Reporting does not rely on its own reporting database, data layer, or report server you will not need to expose anything. Telerik
Reporting uses the ADO.NET data providers and data objects to connect to its data source, so it is not different from any other .NET application connecting to data in the same manner.
- Generally, the
ADO.NET 2.0 data providers are all used in a similar manner. All data
provides come with a standard set of objects. All these objects are
derived from base classes mandated from the ADO.NET 2. This way all
data provider-specific objects have similar and well known interfaces.
The base classes I'm talking about are defined in the
System.Data.Common namespace (System.Data.dll) and here are some of the
most important:
- DbConnection
- DbCommand
- DbDataAdapter
- DbDataReader
A good place to learn more about the ADO.NET 2 data providers is MSDN: http://msdn2.microsoft.com/en-us/library/cy5kfe3c(VS.80).aspx .
The
idea behind the ADO.NET2 data providers is that they simplify their
usage and are interchangeable. This means that they all follow the same
pattern regardless of your connection to SQL, Oracle, Access, MySQL or
other data base. The only thing that you should do is to use the
correct set of objects.
Here is a link to one of our forums that provides a sample demonstrating how to connect to MySQL. Please take a look at it to get a better understanding of the topic.
- Each report is a .NET class. The Report class has a Parameters property that exposes a collection of report parameters. Unless the developer explicitly provides a way for the user to modify those parameters, for example an UI, they cannot be seen by the end users. In other words it is up to the developer to decide what to expose to the end-users and what not, like in any other .NET application.
- The source code comes as part of the Subsription package, which is the best deal in terms of what you get. If you chose to purchase Telerik Reporting with subscription you will get the Gold Support Package and the source code as well. Another benefit is that as a subscription holder you are entitled to all new major and minor releases of Telerik Reporting for one year from the date of purchase.
Non-subscription licenses come with Silver Support (48 hours guaranteed response time) and get only minor version upgrades.
- Yes, it is possible to meet your requirements with our product, even thought you do not have this functionality out of the box.
There are two subtasks:
1. Export the report programmatically to PDF format.
2. Email the resulting stream/file as an attachment.
There is a Knowledge Base article called Saving a report into PDF format programmatically that addresses the first task. And a full sample covering the whole scenario you can find at the forum thread Send a report by email. Additionally there is CodeLibrary entry that provides the implementation of this task.
- Reports are .NET classes and as such they are compiled and stored in .NET assemblies. A new report is added by opening the respective Visual Studio Project, adding the report to it in the same manner that you add a new WebForm for example, designing it with the provided Visual Studio Report Designer and re-compiling the project. The latest version of the .NET assembly has to be replaced on the WebServer if the new report is to show up.
I hope that those answers will provide you with the needed information to get you started.
I strongly suggest that you download the
free trial version of Telerik Reporting and test it in your environment in order to see whether it will fulfill you specific requirements. This is the best way to evaluate the product. The trial version is
fully functional and free to download. It can be used for building real-life applications and its only limitation is a trial message appearing in the different report formats. If you have any other questions, please do not hesitate to contact us again -- we would be glad to help.
Greetings,
Ross
the Telerik team
Check out
Telerik Trainer, the state of the art learning tool for Telerik products.