v9 Assembly > Reports. Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3. ActiveReports Developer 7 > ActiveReports Developer Guide > How To > Page Report How To > Export a Page Report (Rendering Extension). ActiveReports Developer 7 > ActiveReports Developer Guide > Concepts With the PDF export filter, you can use .
|Published (Last):||26 October 2007|
|PDF File Size:||9.28 Mb|
|ePub File Size:||14.84 Mb|
|Price:||Free* [*Free Regsitration Required]|
With the release of ActiveReports 7, we have provided users of Data Dynamics Reports and ActiveReports with an upgrade that adds significant new features.
ActiveReports / ActiveReports v7+ Forum
When we were creating the new viewer control, one thing we didn’t bring over from Data Dynamics Reports was a built-in actovereports from the viewer. This is largely because the number of toolbar buttons on the viewer is already staggering.
If you want to export the current report, we expose an Export method on the viewer control. In a future release we’ll add the export option to the standalone designer and viewer applications as well. But that doesn’t help if you want to provide that functionality now and you don’t want to write the code from scratch.
Well, when we’re done with this post, you’ll have a class that will create a toolbar button for you to provide exports to your users. You can download the complete project here: If you are not using VS, you can just copy the classes out of the project and add the bitmap resource image. Let’s get to it! If you look at the signature of the Export method you’ll see that it takes just a few parameters: We’ll make use of this to implement the export functionality.
Despite the name, these exports can handle both SectionDocument and PageDocument reports, because internally they convert a PageDocument into a SectionDocument at run time.
Something important that we considered in our design was that you may not want to ship all of the exports with your application. That is why we provide two ways of excluding exports that do not require you to modify the toolbar button code tl all.
Let’s start by looking at how to implement a single export.
Export a Page Report (Rendering Extension)
If you open the project, you’ll find the SectionReportExporter class. This abstract class provides the base capability to load expodt the export type at run time, and it returns the IDocumentExportEx object that does the exporting. It also activerwports some helper properties that the UI uses to provide a file dialog filter and default extension.
You may also notice an Export method that will allow you to do more advanced exports in the future, but for now, these stubs throw a NotImplementedException. The reflection code is fairly basic: GetType to load it at runtime.
If it fails, then we know to hide the toolbar button. Once we have the type, we can use the Activator class to create an instance of it, and return it from the GetExporter method as an implementation of IDocumentExportEx. Each of the wxport inherits from this class and passes in the type name, and returns the appropriate file dialog values. Now sctivereports we have the IDocumentExportEx object, we can use it in the toolbar button.
This creates our Save As dialog, passes in our exporter’s preferred file filter and default extension, and then calls activerrports Export method of the viewer control, or “host” in this method. The rest of the code in the project deals with the management of the allowed exports and filters out any exports that aren’t available at runtime.
I’ve made it easy to use this code in your own project. Add the toolbar button image resource, and then the classes. Once you add those to your project, you can add the button with code like the following:. The button loads up the acfivereports exports at run time. If you want to remove some from the list, expory can modify the AvailableExports dictionary on the button see the commented out code above before you add the button to the toolstrip.
Export Method (PdfExport)
If you were to use this same code in the button click event, the exports you remove would still display if the user dropped down the list without clicking the button. I hope you find this code useful. I plan on maintaining it with additional features and bug fixes as we make changes to ActiveReports 7 in the future.
ComponentOne Studio Enterprise, v3. ComponentOne Studio for Xamarin, v3. For more information, contact Amy Reese at press grapecity. A collection that you can modify at runtime to remove exports that you don’t want to make available. Activersports to ensure that each export is available prior to displaying the list to the epxort.
Export exporter, new FileInfo saveAsDlg. Once you add those to your project, you can add the button with code like the following: Remove “PDF” ; viewer1. Insert 3, button ; The button loads epxort the available exports at run time. Login to post a comment.