Specifics of Printouts in PANTHEON
Specifics of Printouts in PANTHEON
Printouts in PANTHEON can be roughly divided into 3 groups:
Documents are printouts intended for customers and employees of the company. Most of them have a similar form, only those in the Personnel and manufacturing modules are slightly different. For these reports, especially orders and invoices, is very important to have good design.
Reports (in the strict sense) are printouts intended for internal use.
Forms are prescribed forms by laws or other legal acts and, as a rule, they should not be changed.
Printouts in PANTHEON have certain specifics that make them behave differently than they would in the usual FastReport. The specifics of reports in PANTHEON are due to:
- Setting in the program (in the administration panel and the reports register, as we already see)
- Entering data onto reports from the program code
- Determining the coordinates (position and size) of the objects on reports and the height of bands in the program code
- The use of features written specifically for PANTHEON
 |
Objects which are referenced from program usually have property "Text" (the text we see in the object in the formatter) the same as the name of the object. Examples are "Text" objects "mTekst", "mKriterij", "mTekst1", and "mKriterij1" in the report title. The program code also fills in the company logo into an object named "fGlava". We must not rename these objects, nor can we change the name of the band on which they are located. |
In addition, in the program code, the coordinates of some objects and the height of the bands are determined. We can not get data for these bands without changing the coordinates. Such bands are usually a standard report header and bands on the recapitulation of documents. In these bands is difficult to change position of objects or add new objects. Data can not be loaded from the program code onto reports that are opening from DPAs.
The bands that have corresponding program code must have assigned "OnBeforePrint" event.
In the event handler procedure "CallQRBeforeBandPrint" the following code is written and must not be deleted:
procedure TitleOnBeforePrint(Sender: TfrxComponent);
begin
CallQRBeforeBandPrint(Sender, TfrxBand(sender).visible);
end;
In the procedure can also be other script. You can also add your own script to this procedure.
|
Data for some datasets are set in the program code. If your dateset on the report has the same name as dataset from program code, an error occurs. Is such a case just rename your dataset on the report. |