PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Principle for printing a report
  • Report with lower and upper bounds
  • Running a query and report based on this query
  • Print destination
  • Printing a component report
  • RPC and independent HFSQL context
  • Nested reports
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Prints a report created with the report editor.
Caution: The WLanguage code required to print the report depends on the data source of report. For more details and examples, see:

Important

With Reports & Queries, you can print a report via one of the following options:
  • by printing directly ( ).
  • by opening the report test window (/ELTIMAGE000083/#).
Therefore, no programming is required to print the report.
In order for the reports created in Reports & Queries to be directly printed from a WINDEV application, this feature must be implemented by the provider of WINDEV application.
The provider can for example include a window allowing the end user to:
  • select a report created in Reports & Queries.
  • run this report.
Note: From version 19, HFSQL is the new name of HyperFileSQL.
// Simple print on printer
iPrintReport(RPT_Invoice)
Reports and Queries
// Print with print preview
iPreview(i100)
iPrintReport(RPT_Invoice)
Syntax
<Result> = iPrintReport(<Report name> [, <Parameter 1> [, <Parameter N>]])
<Result>: Type of result returned by the report (optional)
Versions 20 and later
Value returned by printing the report. This value is returned:
New in version 20
Value returned by printing the report. This value is returned:
Value returned by printing the report. This value is returned:
<Report name>: Character string (with or without quotes)
  • Name of report, defined in the report editor.
  • Physical name of report (including its path) if the compiled code is included in the report.
<Parameter 1>: Optional parameters (the type corresponds to the parameter type)
Optional parameter expected by the report. This parameter was defined in the opening code of report. This parameter can be the name of a view, the name of a memory zone, etc.
Caution: If lower bounds and upper bounds have been specified for the report, the first two parameters must correspond the lower bound and to the upper bound (respectively). $~ ... |
<Parameter N>: Optional parameters (the type corresponds to the parameter type)
Optional parameter expected by the report. This parameter was defined in the opening code of report. This parameter can be the name of a view, the name of a memory zone, etc.
Caution: If lower bounds and upper bounds have been specified for the report, the first two parameters must correspond the lower bound and to the upper bound (respectively).
Remarks

Principle for printing a report

iPrintReport reads the report data source (data files, query, Table control, etc.). iPrintReport prints the Body block for each record. The other blocks are printed when necessary:
  • The Start of document block will be printed at the beginning of document.
  • The End of document block will be printed at the end of document.
  • The Page header block will be printed at the top of each page.
  • The Page footer block will be printed at the bottom of each page.
  • If there is a break, the Body block of the break will be located between the Break header block and the Break footer block.

Report with lower and upper bounds

If the lower and upper bounds were specified when the report was created in the report editor, the first two parameters passed to the report via iPrintReport must correspond to the lower bound and to the upper bound respectively.
Example: a report was created on Customer file. This report browses the file on the "CustomerNum" key item. This report was defined as being bounded, the minimum and maximum bounds being supplied ("Data" tab in the description window of report.
The following code is used to print the report for customers 2 to 5:
iPreview()
iPrintReport(RPT_Customer_Prospects, "2", "5")

Running a query and report based on this query

When printing a report based on a query, the query is not re-run if it was already run. To re-run the query (i.g. add records), simply use HExecuteQuery or iInitReportQuery.

Print destination

The destination of report print can be chosen via iPreview and iDestination.

Printing a component report

To print a component report, use the name of component report (the component being included in the project). For example:
iPrintReport(ComponentReport)
If a conflict occurs with a project element, the name of the element must be prefixed by the name of the component. For example:
iPrintReport(MyComponent.Report)
To use the name of the report in a variable, the name of the component must be specified. For example:
sReport is string = "MyComponent.MyReport"
iPrintReport(sReport)
Reports and Queries

RPC and independent HFSQL context

The access to an HFSQL data file in RPC is not allowed from a report with an independent context.
The "Independent HyperFileSQL context" option must be disabled.
To disable this option in a report, uncheck "The report execution does not affect the browse operations (independent HyperFileSQL context)" in the "Data" tab of report description.
The "Independent HFSQL context" option must be disabled.
To disable this option in a report, uncheck "The report execution does not affect the browse operations (independent HFSQL context)" in the "Data" tab of the report description window.
In an application that uses the remote access, if independent contexts must be used, they must be programmed by HSavePosition and HRestorePosition.
Note: The contexts cannot be copied in RPC. You must use HOpenAnalysis or HConnectRemoteAccess in the new context to access the RPC.

Nested reports

You have the ability to call iPrintReport within the same report. See the help about the Nested reports for more details.
Component : wd240etat.dll
Minimum version required
  • Version 9
This page is also available for…
Comments
Imprimir Numero Nota Fiscal/Danf - 000.001.500.
Aula 1051 - WinDev Relatorio - 041/... - Imprimir Numero Nota Fiscal/Danf - 000.001.500.

iPreview(iapZoom100)
//Vai Mostrar Relatorio Na Tela
iPrintReport(ETAT_Relatorio_Teste)
//Imprimir Relatorio

//Blog com Video e Exemplo

http://windevdesenvolvimento.blogspot.com.br/2017/01/aula-1051-windev-relatorio-041-imprimir.html

https://www.youtube.com/watch?v=3LFsSZwUY5w


De matos
01 Feb. 2017
Exemplo Intervalo Código
Exemplo Intervalo Código

iPreview(ipvZoom100)
IF CBOX_imprimirTodos=True THEN
iPrintReport(RPT_bancos_shared)
ELSE
iPrintReport(RPT_bancos_shared,EDT_BancoInicial,EDT_BancoFinal)

END

//Blog com Video e Imagen

http://windevdesenvolvimento.blogspot.com.br/2016/10/aula-947-windev-curso-relatorio-32.html

https://www.youtube.com/watch?v=yHZbC-bTrRU

De matos
21 Oct. 2016