ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / WLanguage / WLanguage functions / Standard functions / Print functions
  • Initializing the data sources of sequenced reports
  • Managing the page numbers
  • Using global variables
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Adds a report into a sequence of report prints.
Note: Chaining report printouts allows you to print different reports in succession, visible as a single printout in the report viewer. You can add various types of documents in this sequence. For more details, see Sequencing reports.
Example
iDestination(iViewer)
iSequencingAdd(RPT_Report1)
iSequencingAdd(RPT_Report2, 3)
iSequencingPrint()
// Open report viewer
iDestination(iViewer)
FOR EACH Activities 
	// Adds the report of activities for the current activity
	iSequencingAdd(RPT_Activities, Activities.ActivitiesID, Activities.ActivitiesID)
	// Adds the report of devices corresponding  the current activity
	iSequencingAdd(RPT_Devices, Activities.ActivityName)
END
iSequencingPrint()
Syntax
iSequencingAdd(<Report> [, <Parameter 1> [... [, <Parameter N>]]])
<Report>: Character string
State name:
  • Logical name of report, defined in the report editor.
  • Physical name of the report (including its path) if the compiled code is included in the report.
WEBDEV - Server code This parameter must correspond to the logical name of report.
<Parameter 1>: Optional parameters (the type corresponds to the parameter type)
Optional parameter expected by the report. This parameter is defined in the opening code of the report. This parameter can be the name of a view, the name of a memory area, etc.
Caution: If the report includes values with bounds, the first two parameters must correspond to the lower and upper bounds.
Warning: This parameter is passed by state value and not by address..
<Parameter N>: Optional parameters (the type corresponds to the parameter type)
Optional parameter expected by the report. This parameter is defined in the opening code of the report. This parameter can be the name of a view, the name of a memory area, etc.
Caution: If the report includes values with bounds, the first two parameters must correspond to the lower and upper bounds.
Warning: This parameter is passed by state value and not by address..
Remarks

Initializing the data sources of sequenced reports

The states are not executed when the iSequencingAdd function is run: only their names and parameters are stored..
These reports are actually run during the call to iSequencingPrint.
Warning: If any of the reports in the sequence are based on a query, the query must be initialized using function iInitReportQuery in the "Initialization" event of the report (and not before calling function iSequencingAdd)..

Managing the page numbers

If the reports found in the sequencing display the page number, the page numbers will be continued for the different reports.
For example, if the first report of the sequencing is numbered from 1 to 10, the second report will be numbered from 11 to 20, and so on.
To force the page number of a report in the sequence, use iPageNum in the desired report.

Using global variables

Sequenced reports can handle global variables in the different WLanguage events associated with the report. In this case, the value of the global variable taken into account is the one of the report or the print preview.
If the value of a global variable changes between the call to iSequencingAdd and iSequencingPrint, its value in the report will be the last value assigned to it.
Business / UI classification: Neutral code
Component: wd300etat.dll
Minimum version required
  • Version 17
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 11/23/2024

Send a report | Local help