|
|
|
|
|
|
|
|
|
|
- Overview
- Data files tab
- Test data file directory
- Automations
- Automatic reindexing (HFSQL only)
- Data file management mode (HFSQL only)
- Options for Native Connectors
Project description: Data files tab
The project description window allows you to configure various elements of your project. This window includes the following tabs: - The "Project" tab, which allows you to enter general information about the project.
- The "Analysis" tab, which lets you associate one or more analyses with the project and/or a UML model.
- The "Data files" tab which lets you enter information about the data files managed by the application (only available if the project is linked to an analysis).
- The "Live Data" tab, which allows you to configure how the data from the data files is displayed in the different editors.
- The "Languages" tab, which is used to configure the different languages used by the project as well as the options to be used for each language.
  The "Style" tab, which allows you to customize the print preview and to choose the skin template and custom style sheet. You can also configure screen sizes.  The "Skin" tab, which lets you choose the project skin, associated palette, style sheet and external resources. - The "SCM" tab, which is used to manage teamwork (SCM or Git).
- The "Options" tab, which allows you to define the creation, update and save options of the different elements of the project. This tab also allows you to synchronize templates, enable strict mode and define the code style.
- The "Advanced" tab, which allows you to enable "Reports and Queries", configure the AAFs and lock the application.
- The "Compilation" tab, which allows you to configure the compilation options.
- The "Telemetry" tab, which allows you to configure the telemetry options for the project.
This option is not available.
Test data file directory This option allows you to define the directory of data files to be used in test mode: debugging, window Go, page Go or project Go. By default, the directory used is the current configuration directory (subdirectory of the project's EXE directory). It is possible to specify a specific directory. This option is useful if WINDEV is used with the UAC active: in test mode, the application data directory can be used. Automations The following options are available for all data types: - Enable automatic HFSQL help
This option enables automatic error handling in the HFSQL engine. For more details, see Error handling help. - Automatically create the data files when they are opened:
This option automatically creates the data files described in the analysis, if these data files do not exist when using functions that require them to be opened. In this case, the HCreationIfNotFound function is automatically executed.
 This option is supported by Native Connectors for SQL Server, Informix, Sybase, MySQL, MariaDB and PostgreSQL.
Automatic reindexing (HFSQL only) Reindexing a data file can become necessary further to the loss or alteration of index file. An automatic reindex operation can be implemented for the data files. The "Enable the automatic indexing" option allows you to automatically reindex data files by specifying several parameters: - maximum number of records: if the data file contains fewer than XXX records, reindexing is automatic in the event of an index error. This value is set to 100000 by default. The automatic reindex operation is disabled if this variable is set to 0.
- the display of a progress window showing the status of the current reindex operation.
Note: automatic re-indexing is only available for HFSQL Classic and HFSQL Client/Server data files. Data file management mode (HFSQL only) This option defines how the data files of the application are managed. By default, applications created with WINDEV and WEBDEV are multi-user applications: blocking is handled automatically.
It is possible to request "single-user" management: in this case, data files are completely blocked from reading and writing as soon as they are opened. Options for Native Connectors When copying contexts using a Native Connector, if the "Copy connections when copying context" option is checked, each context can have its own connection to the external database server. This option is particularly useful for transactions.
This new feature is available for the following databases: MS SQLServer, Oracle, MySQL, Sybase, Progress, Informix, DB2, SQLite, MariaDB.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|