'Declaration Public NotInheritable Class XlsExport Inherits System.ComponentModel.Component Implements GrapeCity.ActiveReports.Export.IDocumentExport, GrapeCity.ActiveReports.Export.IDocumentExportEx
public sealed class XlsExport : System.ComponentModel.Component, GrapeCity.ActiveReports.Export.IDocumentExport, GrapeCity.ActiveReports.Export.IDocumentExportEx
Optimizing your report for exporting to Excel:
Since Excel is basically a table of rows and columns, and ActiveReports is a free form type output it may be necessary to “optimize?your ActiveReport for Excel exporting. When you want two controls to be in the same column when outputted to excel it is imperative that the two controls have *exactly* the same left value. And it may also help to ensure that the font of the two controls is the same. Attempting to make the height of the two controls similar will often times lead to a cleaner looking output in excel. Similarly if you want two controls to be in the same row when outputted to Excel, you should make sure the two controls have exactly the same Top value, that their font is the same, and that their width is similar if not the same. Using RichText controls on your ActiveReports will often will not have good output in Excel. Using the Page object's drawing methods to draw anything in the margin areas of the export will cause pagination problems. If you draw items on the page, do not draw them in the margin area to keep the pagination accurate when printing excel exported output.
System.Object
System.MarshalByRefObject
System.ComponentModel.Component
GrapeCity.ActiveReports.Export.Excel.Section.XlsExport
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2