LazReport Documentation: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		## Overview
2	2
3	3		LazReport is a group of components to add reporting capabilities to applications. It uses a visual designer to create banded reports and includes a report engine with previewer and an interpreter to run user scripts. The report designer can be invoked at runtime.
4	4
5	5		## License
6	6
7	7		LazReport is based on FreeReport 2.32 and thanks to Fast Reports Inc. it's available under modified LGPL, the same license as the Lazarus LCL. See files lazreport/license.txt, license-rus.txt and license-lazreport.txt for details.
8	8
9	9		## Authors
10	10
11	11		FreeReport was created for Fast Reports Inc.
12	12
13	13		LazReport initial port was made by Olivier Guilbaud.
14	14
15	15		Lazarus integration and fixes by Jesus Reyes A.
16	16
17	17		Many contributors, see lazreport/doc/contributors.txt file
18	18
19	19		## Installation
20	20
21	21		To install LazReport in the Lazarus IDE:
22	22
23	23		1. Open LazReport Package. Menu: Package-\>Open Package File (.lpk)...
24	24		2. Open file components/lazreport/source/lazreport.lpk
25	25		3. Install
26	26
27	27		The next time Lazarus is started, it should show a LazReport tab in the component palette.
28	28
29	29		## Documentation
30	30
31	31		Developer's manual and User Guides specific for LazReport are yet to be written. In the mean time, most LazReport features are described in the FreeReport Developer's Manual (see components/lazreport/doc/fr_eng.odt (or fr_eng.pdf) in your Lazarus installation). Platform specific things described there like OLE objects are not implemented in LazReport, also some examples or pictures make reference to samples available only on Delphi.
32	32
33	33		Until LazReport documentation is elaborated, this Wiki page will be used as a documentation container; maybe in the future the missing documentation could be generated from here. Users are welcomed to add topics that they feel need to be documented.
34	34
35	35		### Operators
36	36
37	37		The following operators are supported:
38	38
39	39		\| Operator type \| Operators \|
40	40		\|----\|----\|
41	41		\| Logical \| \>, \<, BUT, AND, NOT, =, \< \>, \> =, \< = \|
42	42		\| Mathematical\\|\\|-, *, +, MOD, / \| \|
43	43
44	44		### Functions
45	45
46	46		The following functions are available for use:
47	47
48	48		#### Statistical functions
49	49
50	50		SUM(\<X \>)
51	51		Returns the sum of values represented by \<X\>, which is generally a data field.
52	52
53	53		AVG(\<X \>)
54	54		Returns the average of \<X\> values.
55	55
56	56		COUNT
57	57		Count the number of occurrences.
58	58
59	59		MIN(\<X \>)
60	60		Returns the lowest value of all values represented by \<X\>
61	61
62	62		MAX(\<X \>)
63	63		Returns the highest value of all values represented by \<X\>
64	64
65	65		#### Date functions
66	66
67	67		> Note: December 2013: inspection of lr_pars source code seems to indicate these functions work with the current locale date format, which limits interoperability. To do: verify this; extend function with an extra format parameter which defaults to e.g. ISO8601
68	68
69	69		FORMATDATETIME(\<X\>, \<Y \>)
70	70		Returns \<Y\> TDateTime in format \<X\>. \<X\> uses the default syntax for [Lazarus formats](http://www.freepascal.org/docs-html/rtl/sysutils/formatdatetime.html).
71	71
72	72		FORMATFLOAT(\<X\>, \<Y \>)
73	73		Returns the numeric value \<Y\> in format \<X\>. \<X\> uses the default syntax for [Lazarus formats](http://www.freepascal.org/docs-html/rtl/sysutils/formatfloat.html).
74	74
75	75		STRTODATE(\<X \>)
76	76		Returns the TDateTime(? not date?) representation of string \< X \>. \< X \> must be formatted correctly.
77	77
78	78		STRTOTIME(\<X \>)
79	79		Returns the TDateTime time part representation of string \< X \>. \< X \> must be formatted correctly.
80	80
81	81		#### String functions
82	82
83	83		LOWERCASE(\<X \>)
84	84		Returns lowercase \<X\>
85	85
86	86		UPPERCASE(\<X \>)
87	87		Returns uppercase \<X\>
88	88
89	89		NAMECASE(\<X \>)
90	90		Returns \<X\> with initial capitals
91	91
92	92		COPY(\<X\>, \<Y\>, \<Z \>)
93	93		Similar to Pascal Copy: returns string \<X\> from position \< Y \> for \< Z \> characters.
94	94
95	95		#### Numeric functions
96	96
97	97		FRAC(\<X \>)
98	98		Returns the decimal part of number \< X \>
99	99
100	100		INT(\<X \>)
101	101		Returns the integer part of number \< X \>
102	102
103	103		ROUND(\<X \>)
104	104		Returns the number \< X \> rounded to an integer (up? down? nearest integer? banker's rounding?)
105	105
106	106		STR(\<X \>)
107	107		Returns the string representation of number \< X \>
108	108
109	109		#### Logical/boolean functions
110	110
111	111		IF(\<X\>, \<Y\>, \<Z\>)
112	112		Returns \< Y \> if expression \< X \> is true. If false, returns \< Z \>.
113	113
114	114		### Adding your own functions
115	115
116	116		Though it is probably not needed much, LazReport allows you to define your own functions. As mentioned, see [[LazReport Documentation\|LazReport Documentation#Documentation]] for an overview of existing functions.
117	117
118	118		To add your own functions:
119	119
120	120		#### Add template to definition file
121	121
122	122		> Note: This was taken from the Delphi/FastReport/FreeReport tutorial in Portuguese. It should be verified and probably modified to work with current Lazarus/LazReport
123	123
124	124		You need to define your functions following the following template in the file FR.lng (is this still the correct name for Lazreprot?):
125	125
126	126		, FCT = CATEGORY\\|FCT (\<X\> \<Y\>, \<z\>)\\|Help
127	127
128	128		where:
129	129
130	130		- FCT is the function name.
131	131		- CATEGORY is the category name.
132	132		- FCT (\<X\> \<Y\>, \<z\>), is the layout of the required parameters, with a maximum of 3 parameters.
133	133		- Help Is a small help text which should allow the user to understand the purpose of the function.
134	134		- \\| is a separator.
135	135
136	136		Each parameter is separated by commas and can be an expression, a constant, a variable, a field or data. Alphanumeric type constants should be limited by a character. The variables are delimited by and.
137	137
138	138		Data fields are limited to the variables and have the following format:
139	139
140	140		Dataset_Name. "Field_Name"
141	141
142	142		Let's add the SQRT and POS functions by adding the following lines to FR.lng todo: still the same name?
143	143
144	144		SQRT = Mathematics and Trigonometry\\|SQRT(\<X\>)\\|Returns the square root of \<X\>\
145	145		POS = Strings\\|POS(\<X\>,\<Y\>) Returns the position of string \<X\> within string \<Y\>
146	146
147	147		#### Add function source code
148	148
149	149		A function definition is nice, but we haven't specified how these functions work. Therefore, some source code to add the functions POS and SQRT below:
150	150
151	151		``` pascal
152	152		Unit FR_OGFct;
153	153
154	154		interface
155	155
156	156		implementation
157	157
158	158		uses FR_Pars, FR_Class; // Standard declarations needed for Lazreport!! Note: FR_pars etc? Are these names ok?
159	159
160	160		type
161	161		// Our own functions are declared here.
162	162		TfrOGFunctionLibrary = class(TfrFunctionLibrary)
163	163		public
164	164		constructor Create; override;
165	165		procedure DoFunction(FNo:integer procedure; p1, p2,
166	166		p3:Variant; var valley:string); override;
167	167		p3:Variant; var valley:string);
168	168		end;
169	169
170	170		//**************************
171	171		// * TfrOGFunctionLibrary
172	172		constructor TfrOGFunctionLibrary.Create;
173	173		begin
174	174		inherited Create;
175	175		// Add our functions to the list of available functions:
176	176		with List do
177	177		begin
178	178		Add('POS');
179	179		Add('SQRT');
180	180		end;
181	181		end;
182	182
183	183		Procedure TfrOGFunctionLibrary.DoFunction(FNo:Integer procedure;
184	184		p1, p2, p3:Variant; Var valley:String); //valley?
185	185		Var
186	186		Par1, Par2: Varying;
187	187		Result: Variantying; //variantying? variant?
188	188		begin
189	189		Try
190	190		Case FNo of //this is the index of the functions as added in the constructor
191	191		0 :
192	192		begin // POS function
193	193		Par1:=VarToStr(Parser.Calc(p1));
194	194		Par2:=VarToStr(Parser.Calc(P2));
195	195		Result:=Pos(Par1,Par2);
196	196		end;
197	197		1 : // SQRT function
198	198		Result:=SQRT(Parser.Calc(P1));
199	199		end;
200	200		Except
201	201		// String with error details
202	202		Result:='Error in function '+List.Strings[FNo];
203	203		end;
204	204		Val:=VarToStr(Result); // Resulting string
205	205		end;
206	206
207	207		Procedure DoInit;
208	208		begin
209	209		frRegisterFunctionLibrary(TfrOGFunctionLibrary);
210	210		end;
211	211		```
212	212
213	213		Save the report then File\>List and this window will appear:
214	214
215		-	~~<figure>~~
216		-	~~<img src="imagem21.jpg" title="imagem21.jpg" />~~
217		-	~~<figcaption>imagem21.jpg</figcaption>~~
218		-	~~</figure>~~
	215	+	![](/wiki-images/1/10/Imagem21.jpg)
219	216
220	217		You may notice the appearance of a small (...) button, active only in the case of an expression. Click below to open the editor:
221	218
222		-	~~<figure>~~
223		-	~~<img src="imagem22.jpg" title="imagem22.jpg" />~~
224		-	~~<figcaption>imagem22.jpg</figcaption>~~
225		-	~~</figure>~~
	219	+	![](/wiki-images/0/0f/Imagem22.jpg)
226	220
227	221		You may notice the similarity. If you click the Add button it will load the editor parameters:
228	222
229		-	~~<figure>~~
230		-	~~<img src="imagem23.jpg" title="imagem23.jpg" />~~
231		-	~~<figcaption>imagem23.jpg</figcaption>~~
232		-	~~</figure>~~
	223	+	![](/wiki-images/2/23/Imagem23.jpg)
233	224
234	225		Depending on the number of parameters, you have more or less edit areas. The (...) button makes it possible to open the expression generator to set the parameter.
235	226
236	227		### Export Filters
237	228
238	229		LazReport has the ability to save the report displayed in the preview window using a user-defined format. It has an extension mechanism with support for plugins that can be used to add any amount of export filters.
239	230
240	231		An export filter is a specially designed class which is registered in LazReport and allows you to save the report using one or more formats.
241	232
242	233		When LazReport is installed, it includes some filters ready for use, these are: TfrTextExportFilter for exporting report as plain text, TfrCSVExportFilter used for exporting the report as CSV format and TfrHTMExportFilter for exporting the report as simple html file. Also included are some packages that provide additional filters, these are (see Menu Package-\>Install/Uninstall Packages ...): lrCairoExport (components/lazreport/source/addons/cairoexport/lrCairoExport.lpk) which provides support for exporting to PDF and PS formats by using the Cairo Graphics Library and lr_extexp (components/lazreport/source/addons/imgexport/lr_extexp.lpk) with support for improved html export and some image formats like BMP, JPG and PNG. Also included in LazReport is the LazReportPDFExport (components/lazreport/source/addons/pdfexport/LazReportPDFExport.lpk) package, this package provides PDF export using [[PowerPDF]] which is available in Lazarus-CCR repository.
243	234
244	235		A filters package is installed in the same way as any other Lazarus Package; after restarting Lazarus, the filters (usually) appear as icons in the LazReport tab on the Component Palette.
245	236
246	237		An export filter is added to your application by simply dragging one of these icons to a form or data module where TfrReport component exists, this is automatically registered and remains ready to use.
247	238
248	239		This can also be done manually by including the export filter unit name in the Uses clause of the unit where TfrReport is used.
249	240
250	241		LazReport export filters are invoked using one of two ways:
251	242
252	243		1. Save the report in the preview window. Using this method (pressing the Save button) when the Save As dialog is presented, the user can choose a format from the list of registered formats. The list is populated by all registered export filters.
253	244		2. Through code using the TfrReport ExportTo method. See below for an example:
254	245
255	246		``` pascal
256	247		if TheReport.PrepareReport then
257	248		TheReport.ExportTo(TfrHTMExportFilter, 'exportedfile.html');
258	249		```
259	250
260	251		Where TheReport holds an instance of TfrReport component. In this sample a TfrHTMExportFilter is used to generate a file named 'exportedfile.html'. It's not necessary to prepare the report again if it has been prepared previously.
261	252
262	253		In order to use TfrHTMExportFilter the developer has to drag and drop an instance of the TfrHTMExportFilter component from the LazReport tab in the component palette to the form in the Form Designer. As an alternative the unit lr_e_htm.pas file can be added to the unit uses clause.
263	254
264	255		Since LazReport 0.9.6, export filters support has been enhanced: now export filters can take parameters which users can customize either by changing values directly or by presenting the end user some UI. In order to make changes in parameters, the developer can create an event handler for TfrReport.OnExportFilterSetup event, available by selecting the TfrReport component and selecting the Events tab in Object Inspector.
265	256
266	257		The OnExportFilterSetup (of type TExportFilterSetup) event handler takes an argument sender of type TfrExportFilter, in order to use this type, the lr_class.pas unit must be added to the unit uses clause. All ExportFilter clases share this event and the developer has to type-cast the sender argument to the desired export filter class, for example:
267	258
268	259		``` pascal
269	260		if sender is TfrHTMExportFilter then
270	261		begin
271	262		TfrHTMExportFilter(sender).UseCSS := false;
272	263		end;
273	264		```
274	265
275	266		Below a description of available export filters.
276	267
277	268		#### TfrExportFilter
278	269
279	270		TfrExportFilter is the base class of all export filters, and defines two properties that can be modified by the developer in the OnExportFilterSetup event:
280	271
281	272		- BandTypes: TfrBandTypes. this is a set of band types, only bands included in this set are actually exported; the other bands on the report will be ignored. Using this property a developer could for example export only the master band content, leaving titles, headers and footers out of exported output by doing:
282	273
283	274		``` pascal
284	275		sender.BandTypes := [btMasterData];
285	276		```
286	277
287	278		By default, all bands are processed but TfrCSVExportFilter changes this property to process only master header, column header and master data bands.
288	279
289	280		- UseProgressbar: boolean. This property enables or disables showing the progress bar while processing the export filter. This property is false by default.
290	281
291	282		#### TfrTextExportFilter
292	283
293	284		inheritance: TfrExportFilter \<- TfrTextExportFilter\
294	285		located in: components/lazreport/source/lr_e_txt.pas file included with the LazReport package.
295	286
296	287		TfrTextExportFilter is the base class of text based export filters. This export filter tries to make a text representation of a graphical report by fitting the original graphical coordinates into a more coarse grid where each unit is of "UsedFont" pixels, depending on the value of UsedFont value, the exported output may more or less represent the layout of objects in graphical report. Beside the properties inherited from TfrExportFilter class, TfrTextExportFilter define two more properties.
297	288
298	289		- UsedFont:integer. this property define the pixel dimensions on the output grid, objects on report are fitted into this grid by reclaculating each x and y position. The default value is 10, if user changes this value to 0 or less, LazReport will show automatically a dialog asking for the UsedFont value, if user enter a invalid value, a 10 value will be used. The 10 value is used because is the value that better fits the usual reports which are made with fonts 10-13 points.
299	290		- UseBOM:boolean. This property enable the inclusion of UTF-8 Byte Order Mark character at the start of text output (see [BOM](http://en.wikipedia.org/wiki/Byte_order_mark)) needed by some editors/viewers, by default no BOM is used in exported output.
300	291
301	292		#### TfrCSVExportFilter
302	293
303	294		inheritance: TfrExportFilter \<- TfrTextExportFilter \<- TfrCSVExportFilter\
304	295		located in: components/lazreport/source/lr_e_csv.pas file included in LazReport package.
305	296
306	297		This special text export filter produces Comma Separated Value output (actually any character can be used as separator), it differs from its ancestor in that it doesn't try to create text layout representation of graphical report, instead, for each record output it tries to guess the fields order from the source report, it then produce a list of fields using a separator defined by the user. Beside the properties inherited from its ancestor classes it defines some properties to customize the generated output.
307	298
308	299		- QuoteType:TfrQuoteType. This property controls whether the generated field value should be wrapped using specified quote char or not. Possible values are qtNone, qtQuoteChar and qtAutoQuote. With qtNone the field value is never wrapped, qtQuoteChar will use the character specified by property QuoteChar, any instance of QuoteChar already present in field value is duplicated. qtAutoQuote first try to find if any instance of separator or QuoteChar is already present in field value, if affirmative it behaves as if qtQuoteChar has been specified, on the contrary case, the field value is not wrapped just as if qtNone has been specified. QuoteType property is set to qtQuoteChar by default.
309	300		- QuoteChar:TUTF8Char. This holds the character to be used to wrap the field value in case of QuoteType of value qtQuoteChar has been specified or deduced if qtAutoQuote is set. Any instance of this character in the field value will be duplicated. by default QuoteChar is set to the " character.
310	301		- Separator:TUTF8Char. This is the character used to separate the fields in each record, by default is set to the ',' (COMMA) character but any UTF-8 valid character could be used. Some CSV files are actually TAB separated files, to get this, set Separator:=#9;
311	302
312	303		The CSV exporter do not use the inherited UsedFont property value so any value set will be ignored. With default property values, TfrCSVExportFilter will produce Excel compatible files, the only caveat is that Excel will not recognize the file as UTF-8 encoded. To force Excel to recognize the encoding automatically, set the property UseBOM to true.
313	304
314	305		#### TfrHTMExportFilter
315	306
316	307		inheritance: TfrExportFilter \<- TfrTextExportFilter \<- TfrHTMExportFilter.\
317	308		Located in: components/lazreport/source/lr_e_htm.pas in LazReport package.
318	309
319	310		This special text export filter produces valid "HTML 4.01 Transitional" output. Currently it defines only one additional property.
320	311
321	312		- UseCSS:boolean. This property controls whether or not the produced output include CSS information, this property is set to true by default.
322	313
323	314		### Scripting Language
324	315
325	316		A simple scripting language (interpreter) for a Pascal-like language is included in LazReport.
326	317
327	318		Some notes:
328	319
329	320		- the interpreter seems to expect semicolons after each line
330	321		- the interpreter cannot handle nested if statements
331	322
332	323		Example:
333	324
334	325		``` pascal
335	326		if [[PAY]>0] then begin
336	327		if[[LATE_FEE]=1] then Text:=[MSGL2];
337	328		else Text:= [MSGL1];
338	329		end;
339	330		```
340	331
341	332		The above won't compile, while this will:
342	333
343	334		``` pascal
344	335		if[[LATE_FEE]=1] then Text:=[MSGL2]
345	336		else Text:= [MSGL1];
346	337		```
347	338
348	339		Source: [forum thread](http://forum.lazarus.freepascal.org/index.php/topic,22902.0.html).
349	340
350	341		### Examples
351	342
352	343		You can find some examples in your Lazarus installation under components\lazreport\samples.
353	344
354	345		#### Running total
355	346
356	347		To calculate the total for values of each page added to the total on the previous page, follow these steps:
357	348
358	349		- Make sure you have a report with a master data band connected to a dataset
359	350		- Place a text inside that band and double click to open its editor.
360	351		- In the editor, check the script option on the top left.
361	352		- In the script window, paste the following code
362	353
363	354		``` pascal
364	355		IF [Line#] = 1 then RunTotal := [Dbf1."MTH_NO"]
365	356		else RunTotal := RunTotal +[Dbf1."MTH_NO"];
366	357		```
367	358
368	359
369	360		of course you need to replace \[dbf1."MTH_NO"\] with your field, the one you want a running total.
370	361
371	362		- Click OK to save the changes.
372	363		- Reopen the editor by double clicking on the text object
373	364		- Click the "Variable" button.
374	365		- Select the fr variables category in the drop down combo.
375	366		- Double click the RunTotal variable to be placed on Memo.
376	367		- Click OK and then press Preview.
377	368
378	369		Source: [Issue \#17198](https://bugs.freepascal.org/view.php?id=17198)
379	370
380	371		### Tutorial
381	372
382	373		Please see [[LazReport Tutorial]].
383	374
384	375		### See also
385	376
386	377		- [Creating and printing a report](http://www.pp4s.co.uk/main/tu-db-firebird-demo3.html)
387	378
388	379		## Report Designer
389	380
390	381		- Menu: File-\>Save As ...
391	382		- Templates Notice:
392	383		- While saving the current report, the user can select an arbitrary directory in the Save As dialog, in the case of templates (.lrt extension), the selected directory is ignored. Templates are always stored in the Templates Directory. The Templates Directory value can be set by either changing the frTemplateDir global variable (lr_desgn.pas unit) or by setting the TemplateDir property in a TfrDesigner component. The TemplateDir property will overwrite the frTemplateDir global variable if both are used. The Templates Directory can be an absolute path or a relative to program path directory, if this directory do not exists, LazReport will try to create it on the first use. If the TemplateDir property or the frTempateDir variable are not set, LazReport will try to save the templates in the program directory.
393	384		- Binary templates format (.frt) is not recommended, as binary formats are hard to keep compatible with newer (or older) LazReport versions. If possible use .lrt file extension (XML file format).
394	385
395	386		## Quick Start
396	387
397	388		### Report Records from a Dataset
398	389
399	390		In this sample we will design a report to print records from a dataset derived component (TDbf, TSQLQuery, TZTable, TZQuery, Etc.). First it's assumed that LazReport is already installed and the dataset component, called "Dbf1" here, is already configured and active.
400	391
401	392		1. From LazReport tab, select TfrReport component and drop it in Form Designer, it will be named "frReport1".
402	393		2. Drop a TfrDbDataset component, it will be named "frDbDataset1"
403	394		3. Drop a TButton, it will be named Button1, change its name to "btnShowReport"
404	395		4. With frDbDataset1 selected in Object Inspector select "Dbf1" for the "Dataset" property
405	396		5. Now select frReport1 and using the same procedure link its "Dataset" property to "frDbDataset1":
406		-	~~<center>~~
407		-
408		-	~~<figure>~~
409		-	~~<img src="lrformsetup.png" title="lrformsetup.png" />~~
410		-	~~<figcaption>lrformsetup.png</figcaption>~~
411		-	~~</figure>~~
412		-
413		-	~~</center>~~
	397	+	![](/wiki-images/4/46/Lrformsetup.png)
414	398		6. Right Click frReport1 and select "Design Report" from the menu, LazReport report designer will appear.
415	399		7. From Designer window, select menu Tools-\>Tools-\>Insert DB Fields, Insert fields Dialog will appear.
416	400		8. In field list select the fields you want in the report
417	401		9. Check "Include Headers" and "Include Bands" options, the result should be something like this:
418		-	~~<center>~~
419		-
420		-	~~<figure>~~
421		-	~~<img src="lrinsertfieldsdialog.png" title="lrinsertfieldsdialog.png" />~~
422		-	~~<figcaption>lrinsertfieldsdialog.png</figcaption>~~
423		-	~~</figure>~~
424		-
425		-	~~</center>~~
	402	+	![](/wiki-images/7/7d/Lrinsertfieldsdialog.png)
426	403		10. Press the "Ok" button, LazReport will arrange bands and fields like this:
427		-	~~<center>~~
428		-
429		-	~~<figure>~~
430		-	~~<img src="lrreportwithfields.png" title="lrreportwithfields.png" />~~
431		-	~~<figcaption>lrreportwithfields.png</figcaption>~~
432		-	~~</figure>~~
433		-
434		-	~~</center>~~
	404	+	![](/wiki-images/4/43/Lrreportwithfields.png)
435	405		11. Press the preview button ![](/wiki-images/b/bb/Lrprevieweye.png), LazReport will then arrange things and show:
436		-	~~<center>~~
437		-
438		-	~~<figure>~~
439		-	~~<img src="lrpreviewreport.png" title="lrpreviewreport.png" />~~
440		-	~~<figcaption>lrpreviewreport.png</figcaption>~~
441		-	~~</figure>~~
442		-
443		-	~~</center>~~
	406	+	![](/wiki-images/4/43/Lrpreviewreport.png)
444	407		12. Save the report with Menu File-\>Save, select the same directory as the current project and name it as listing1.lrf
445	408		13. Close the report designer.
446	409		14. Double click btnShowReport and type the following code:
447	410
448	411		``` pascal
449	412		frReport1.LoadFromFile('listing1.lrf');
450	413		frReport1.ShowReport;
451	414		```
452	415
453	416		## Bug reports
454	417
455	418		Please report problems using the [lazarus/freepascal bugtracker](http://www.freepascal.org/mantis/main_page.php), project: "Lazarus Packages", Category "LazReport".
456	419
457	420		For patches, please submit a bug report and attach the patch to it.
458	421
459	422		---
460	423		From the Free Pascal wiki, page "LazReport Documentation", as it stood on 2022-02-05 after a change by Slawek, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).

Back to history