|
|
|
|
|
|
|
|
|
|
- Overview
- How to?
- Test the current report
- Note: Minimizing (or not) the editor during the test
- Stopping the test of a report
- Notes
- Directory of the data files used for testing
- Managing passwords (analysis or data file)
The test of a single report allows you to run the current report in WINDEV, WEBDEV or WINDEV Mobile. Like for the project test, you can start the debugger if a problem occurs. Remark: The status test is performed on the development workstation only.. The data used for test corresponds to the data found on the development computer. The following WLanguage events are run when testing a report: - Initialization of the project.
- Events associated with the report.
- Events associated with the blocks of the report.
- Events associated with the controls of the report.
Note The report test is only available for reports based on a query, a data file, a text file and reports associated with no data source. For the other types of reports, you must run the test of the element (window, page or project) from which the report is printed. Test the current report To run the test of the current report: - Click
 in the quick access buttons (F9 key). - A screen allows you to choose the print mode of the report: The available options are:
- Report viewer: displays the report on screen as it will be printed.
- Printer: the status is printed directly on the default printer.
- RTF file The report is saved in an RTF file and displayed in a text editor (Word, for example).
- HTML file The status is saved in an HTML file and displayed in the Internet browser installed on the workstation.
- PDF file: the report is saved in a PDF file and displayed in a PDF editor (e.g. Acrobat Reader).
- Generic PDF file: the report is saved in a generic (printer-independent) PDF file and displayed in a PDF editor (e.g. Acrobat Reader).
For more details on these different modes, see Print modes of a report. - Choose the print mode and validate. If your report is not saved, WINDEV, WEBDEV or WINDEV Mobile automatically proposes to save it under the name given in the report creation wizard.
- Specify the additional information if necessary:
- If the report is bounded, a window allows you to enter the report bounds. For more details, see Bounded report.
- If the report is based on a query with parameters, a window allows you to enter the query parameters. For more details, see Report based on a query with parameters.
- If the report expects parameters, give a default value to the parameters in the declaration of parameters. For more details, see Passing parameters to a report.
Note: You can relaunch the last test performed (window, query, report, etc.) from any element in the project, using the "GO . Relaunch last test" option in the quick access buttons. Note: Minimizing (or not) the editor during the test During a test, the editor is minimized by default. Depending on the hardware configuration (wide screen, 2 screens, etc.), you may not need to minimize the editor. To keep the editor opened: - On the "Home" tab, in the "Environment" group, expand "Options" and select "Code editor options".
- On the "Debugger" tab, uncheck "Minimize editor in test mode".
- Validate.
Stopping the test of a report There are multiple methods to stop the test: - 1st method: Close the report viewer in which the current test status is displayed. The current editor at the time the test was started is displayed.
- 2nd method: Return to the editor using the taskbar or the Alt + Tab keystroke combination and confirm that you wish to stop the test.. The current editor at the time the test was started is displayed.
- 3rd method: Return to the editor using the taskbar or the Alt + Tab key combination and click on the
 icon ("End test" option) in the "Debugger" pane.
Directory of the data files used for testing To specify the data files used when running the application test in the editor: - Open the project description window. To do so, go to the "Project" tab, "Project" group, and select "Description".
- In the "Data files" tab, select the location of the test data files:
- Directory of the current configuration or current directory (default setting): Data files will be located in the sub-directory corresponding to the current configuration (sub-directory of the project's EXE directory).
- Specific directory: Data files will be located in the specified directory.
Managing passwords (analysis or data file) No password is requested when running the test of a report linked to a password-protected data file. The necessary passwords must be specified through programming in the "Open" event of the report: - If the report is linked to one or more password-protected data files, the password must be specified with HPass.
- A WLanguage error occurs during the test if the passwords are not specified in the "Open" event of the report.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|