Importing C1Report into C1PrintDocument has the following limitations:
• Only a report definition contained in an XML file can be imported. That is, if an application that produces a report in code via C# or VB.NET handlers attached to C1Report events, that report cannot be imported into C1PrintDocument.
• In C1Report, if there is no printer installed, and CustomWidth and CustomHeight are both set to 0, the paper size is always set to Letter (8.5in x 11in). In C1PrintDocument, the paper size is determined based on the current locale, for example, for many European countries it will be set to A4 (210cm x 297cm).
• Scripting limitations:
• The Font property is read-only.
• The Section property is read-only.
• The Font property is read-only.
• The LineSpacing property does not exist.
• The Field.Subreport property is read-only.
• If the LinkTarget property contains an expression, it will not be evaluated and will be used literally.
• The SubreportHasData property does not exist.
• The LinkValue property does not exist.
• The ColumnLayout property is not supported, columns always go top to bottom and left to right.
• The LabelSpacingX property does not exist.
• The LabelSpacingY property does not exist.
• The OverlayReplacements property does not exist.
• In OnFormat event handlers, properties that affect the pagination of the resulting document should not be changed. For example, ForcePageBreak cannot be used.
• The dialog box for entering the report's parameters is not shown. Instead, default values are used. If the default is not specified, it is determined by the type of the parameter, for example, 0 is used for numbers, empty string for strings, current date for dates, and so on.
• Database fields cannot be used in PageHeader and PageFooter.
• In C1Report, in multi-column reports the report header is printed across all columns; in C1PrintDocument, it will be printed only across the first column.
• Across is not supported for columns.
|
