ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / Editors / Project editor / Environment
  • Overview
  • How to?
  • Enabling the programming standard error
  • Fixing a programming standard error
  • Overriding a programming standard error
  • Deactivating a programming standard error
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Overview
Programming standard errors inform you of potential problems detected when saving windows, pages, reports or when recompiling the project:
  • Functions kept for backward compatibility.
  • Access to HFSQL from the interface.
  • Using WLanguage object functions.
By default, the programming standard errors are not enabled for each new created project.
How to?

Enabling the programming standard error

The programming standard errors can be enabled:
  • from the project description.
  • from the pane of compilation errors.
To enable the programming standard errors from the project description:
  1. Open the project description window (go to the "Project" tab, "Project" group and click "Description").
  2. On the "Compilation" tab, in "Programming standard", check the desired options:
    Programming standard
    • Classic or prefix syntax It is possible to:
      • Allow both: In this case, no programming standard error will be displayed.
      • Indicate use of prefix syntax: A programming standard error will appear if prefix syntax is used (e.g., "ListControl.Add").
      • Indicate use of standard syntax: A programming standard error will appear if standard syntax is used instead of an available prefix syntax.
    • New in SaaS
      Report vocabulary mix-ups A programming standard error will be displayed if a function with a name corresponding to the "historical" vocabulary is used in a project displayed in an environment using a generic vocabulary (#Team Table).
      Note: This feature is only available from WINDEV Suite SaaS 2025 - Update 3.
      For more details, see Using new features exclusive to WINDEV Suite SaaS 2025.
    • Indicate when the Business logic and UI code are mixed: If this option is checked, code mixing errors will be enabled on all project elements. For more details, see Splitting Business logic / UI code.
    • Indicate use of insecure threads: If this option is checked, there will be error messages for unsafe threads. For more details, see Thread (Variable type).
    • Indicate the WLanguage functions kept for compatibility: If this option is checked, WLanguage functions kept for backward compatibility are indicated in the programming standard errors (e.g. TreeSort_55).
      Reminder: Functions kept for compatibility may no longer be supported in a future version.. It is recommended to use the corresponding new function.
    • Indicate shared multilingual messages: If checked, this option allows you to quickly identify shared multilingual text, by generating a compilation error. This option should be used when converting multilingual text to format 27 and higher. For more details, see Translating programming text.
    • New in version 2025
      Indicate strings that should be secret: If this option is checked, any functions that handle passwords, private keys or tokens will be highlighted. For these parameters, you can use secret keys defined in the secret string vault. For more details, see Secret string vault.
  3. Validate.
To view programming standard errors in the compilation errors pane:
  1. Display the "Compilation errors" pane: under the "Home" pane, in the "Environment" group, pull down "Panes" and select "Panes" then "Compilation errors".
  2. Click Programming standard error.
The programming standard errors are checked:
  • whenever saving a window, a page or a report.
  • whenever recompiling the project.

Fixing a programming standard error

The programming standard errors are listed in the pane of compilation errors.
To fix the programming standard errors:
  1. Double-click on the error displayed in the "Compilation error" pane. The element containing the control or the code where the problem occurs is opened in the editor. The description of the corresponding control is displayed.
  2. Fix the problem.

Overriding a programming standard error

By default, the programming standard defined for the project options is applied to all project elements. However, you can override this standard for each element (window, report, page, internal component).
To override the programming standard of a window or page:
  1. Open the element description window.
  2. On the "Details" tab, click "Programming standard".
  3. In the window that is displayed, select the process mode of each option:
    Overriding a programming standard error (window or page)
    • Same as project: The project programming standard is applied.
    • Indicate: The programming standard is always applied for the corresponding element.
    • Don't indicate: The programming standard is never applied for the corresponding element.
  4. Validate the programming standard window.
  5. Validate the window description.
To override the programming standard of a report:
  1. Open the report description window.
  2. On the "Options" tab, click "Programming standard".
  3. In the window that is displayed, select the process mode of each option:
    Overriding a programming standard error (report)
    • Same as project: The project programming standard is applied.
    • Indicate: The programming standard is always applied for the corresponding element.
    • Don't indicate: The programming standard is never applied for the corresponding element.
  4. Validate the programming standard window.
  5. Validate the report description.
To override the programming standard of an internal component:
  1. Open the description of the internal component ("Description" option of the internal component displayed in the project explorer).
  2. On the "Compilation" tab, specify the programming standard options to be overridden:
    • Same as project: The project programming standard is applied.
    • Indicate: The programming standard is always applied for the corresponding element.
    • Don't indicate: The programming standard is never applied for the corresponding element.
  3. Validate the description of the internal component.
New in SaaS

Deactivating a programming standard error

To disable a programming standard error:
  1. In the "Compiler errors" pane, select the programming standard error to be disabled.
  2. Display the error context menu:
    • "Disable this error" is used to disable the selected error.
    • the "Disable this error and all identical errors" option disables the error and all errors of the same type in the current project.
To view the list of disabled errors:
  1. In the "Compilation errors" pane, display the context menu (right-click).
  2. Select "List of disabled errors".
To re-enable (if necessary) one or more errors in this list, all you have to do is uncheck the errors that must be re-enabled and validate the window.
Minimum version required
  • Version 23
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 05/14/2025

Send a report | Local help