PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Overview
  • How to?
  • Testing the current report
  • Remark: Minimizing (or not) the editor during the test
  • Stopping the test of a report
  • Notes
  • Directory of data files used for test
  • Managing passwords (analysis or data file)
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Overview
The test of a single report allows you to run the current report in WINDEV, WEBDEV or WINDEV Mobile. Like for the project test, the debugger can be started as soon as a problem occurs.
Remark: The test of the report is run on the development computer 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.
Remark: The test of the report is available for the reports based on a query, a data file, a text file and for the 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.

Important

During the test of a report in Reports & Queries, the initialization event of the project is run.
How to?

Testing the current report

To test the current report:
  1. Click Go in the quick access buttons (F9 key).
  2. A screen allows you to choose the report print mode:
    Print mode
    The available options are:
    • Report viewer: used to preview the report as it will be printed.
    • Printer: the report is printed on the default printer.
    • HTML file: the report is saved in an HTML file and displayed in the Internet browser installed on the computer.
    • RTF file: the report is saved in an RTF file and displayed in a text editor (Word for example).
    • PDF file: the report is saved in a PDF file and displayed in a PDF viewer (Acrobat Reader for example).
    • Versions 17 and later
      Generic PDF file: the report is saved in a generic PDF file (independent of the printer) and displayed in a PDF viewer (Acrobat Reader for example).
      New in version 17
      Generic PDF file: the report is saved in a generic PDF file (independent of the printer) and displayed in a PDF viewer (Acrobat Reader for example).
      Generic PDF file: the report is saved in a generic PDF file (independent of the printer) and displayed in a PDF viewer (Acrobat Reader for example).
    For more details on these different modes, see Print modes of a report.
  3. 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.
  4. 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 on 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.
Versions 21 and later
Remark: The last test run (window, query, report, ...) can be re-run from any project element via "GO .. Re-run the last test" found in the quick access buttons.
Run the test again
New in version 21
Remark: The last test run (window, query, report, ...) can be re-run from any project element via "GO .. Re-run the last test" found in the quick access buttons.
Run the test again
Remark: The last test run (window, query, report, ...) can be re-run from any project element via "GO .. Re-run the last test" found in the quick access buttons.
Run the test again
Versions 18 and later

Remark: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" tab, in the "Environment" group, expand "Options" and select "Options of the code editor".
  2. In the "Debugger" tab, uncheck "Minimize editor in test mode".
  3. Validate.
New in version 18

Remark: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" tab, in the "Environment" group, expand "Options" and select "Options of the code editor".
  2. In the "Debugger" tab, uncheck "Minimize editor in test mode".
  3. Validate.

Remark: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" tab, in the "Environment" group, expand "Options" and select "Options of the code editor".
  2. In the "Debugger" tab, uncheck "Minimize editor in test mode".
  3. Validate.

Stopping the test of a report

Several methods can be used to stop the test:
  • 1st method: Close the report viewer that shows the report being tested. The current editor at the time the test was started is displayed.
  • 2nd method: Go back to the editor with the taskbar (or press Alt + Tab) and confirm the end of the test. The current editor at the time the test was started is displayed.
  • 3rd method: Go back to the editor via the taskbar or with Alt + Tab and click on Stopping the test ("End the test") in the "Debugger" pane.
Notes

Directory of data files used for test

To specify the data files used when running the application test in the editor:
  1. Open the project description: on the "Project" tab, in the "Project" group, click "Description".
  2. In the "Files" tab, select the location of test data files:
    • Directory of the current configuration or current directory (default): The data files will be located in the subdirectory corresponding to the current configuration (subdirectory of the project EXE directory).
    • Specific directory: The data files will be found 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 "Opening" 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 "Opening" event of the report.
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment