|
|
|
|
|
|
|
|
|
|
- Overview
- "General" tab
- "Details" tab
- "Logging" tab
- "Archiving" tab
- "Language" tab
- "International" tab
- "Options" tab
- "Compilation" tab
Analysis description window
The analysis description window includes all the characteristics and options of the current analysis. To open the analysis description window: - on the "Analysis" tab, in the "Current element" group, click "Description".
- in the context menu of the data model editor, select "Analysis description".
The data model description window presents different options grouped by tabs. The "General" tab provides general information about the current analysis. The available details are: - Analysis name: Name of the current analysis. This name can be modified. In this case, the analysis will be renamed. The data model editor then suggests associating the renamed analysis with the current project.
- Caption: Text associated with the current analysis.
- Directory: Directory in which the analysis is saved.
- Full name: Full name of the "wda" file corresponding to the current analysis.
- Created by: Author of the analysis. The creation date and time are also indicated. This information cannot be modified.
- Updated by: Name of the user who modified the analysis. The modification date and time are also indicated. This information cannot be modified.
- Analysis GUID: Analysis ID. This information cannot be modified. You can also get this information programmatically, using the GUIDAnalysis property.
The "Details" tab allows you to view and modify the analysis access options. The available details are: - Editor password: Password used to open the analysis in the data model editor.
- Runtime password: Analysis password used at runtime. This password is requested when opening the analysis in the HFSQL Control Center or with the HOpenAnalysis function, for example.
- Default data file directory: Default directory used to create the data files of the current analysis.
- Description: Analysis description to be included in the technical documentation.
- Analysis linked to a WINDEV 5.5 or WEBDEV 1.5 analysis: If the analysis is compatible with WINDEV 5.5 or WEBDEV 1.5, you can select the corresponding analysis and its password, if necessary.
The "Logging" tab lets you view and modify general data file logging options. The available details are: - Directory and password for files containing access history (JournalOperation and JournalIdentification files).
- Directory containing replica descriptions for replicated data files.
The "Archiving" tab allows you to enable or disable the analysis archiving feature. The "Language" tab allows you to get and set the programming language used by the analysis. The default language is WLanguage. You can use other programming languages. In this case, you need to specify the source generation directory. The "International" tab allows you to select the languages supported by the analysis. Analyses can support more languages than the associated project. This can be necessary for analyses shared by projects that support different languages. You can synchronize the languages of the analysis with the languages of the current project by clicking "Synchronize with project". The "Options" tab allows you to view and change the display, synchronization and editing options in the data model editor. The available details are: - Display item details in the graph: Shows an icon next to the name of the item in the data model, to indicate the type of item.
- Links point to the linked keys: Links defined in the editor are shown between linked keys in the data files.
- Show items with the same name in other data files: When creating an item, opens a list of items with the same name in other data files in the current analysis.
- Restore deleted data files: When you create a data file with the same name as a recently deleted data file, a window opens and lets you choose between creating a new file or restoring the old data file along with its items.
- Restore deleted items: When you create an item with the same name as a recently deleted item, a window opens and lets you choose between creating a new item or restoring the old item.
- Check subscription of data files when opening analysis: Checks if changes were applied in the dictionary that contains the subscriber data file.
Note: This option is kept for backward compatibility. It requires a personal Dictionary. - Synchronization: Indicates if the project and the analysis should be synchronized when changes are made to the analysis. This synchronization can be automatic or appear as a suggestion (default).
- When opening the project: Desired action when the project opens:
- Restore last analysis status,
- Never open the analysis,
- Always open the analysis.
- Propose to synchronize with the external databases: Shows an automatic suggestion to synchronize data coming from an external database. Simply indicate how often the data should be synchronized. For more details, see Synchronize analysis with external databases.
- Don't propose the SDD after the generation: No longer suggests updating data files after generating the analysis.
- Allow special characters in item names: Allows or prevents you from using special characters in the name of data file items. Please note that this option is not compatible with the HFSQL engine.
- Automatically suggest Metatypes when creating the item: Automatically suggests the metatypes defined in the analysis when creating an item.
- Unicode: Allows or prevents using Unicode characters in the analysis AND executing stored procedures in Unicode mode.
The "Compilation" tab lets you view and change the compilation options of stored procedures defined in the data model editor. . The available options are as follows: - Enable compilation errors for 64-bit compatibility: Shows errors that affect applications intended for 64-bit platforms.
- Enable compilation errors for Linux compatibility: Shows errors that affect applications intended for Linux.
- Programming standard: Standard or prefix syntax: You can:
- 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.
- Programming standard: 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.
- Allow "[% %]" in strings: This option allows the direct input of a variable name in a character string (also called "dynamic string construction"). To do so, use the following syntax:
For example:
IF YesNo(Yes, "Do you confirm the creation of customer [%sCustomerName%]") = No THEN
RETURN
END
grTooltip(GR_Deadline, grTooltipFormat, "[%CATEGORY%]" + CR + CR+ "[%VALUE%]" + " H")
grTooltip(GR_Deadline, grTooltipFormat, -%"[%CATEGORY%]" + CR + CR + -%"[%VALUE%]" + " H")
- Allow nullable types: Enables nullable types in a WINDEV, WEBDEV or WINDEV Mobile project. Allowing nullable types in a project changes the way your project handles null values. For more details, see NULL values: Allowing nullable types.
- Arrays: deep copy
This option makes arrays local by default. This means that the '=' operator performs a deep copy of the values in the array.
If necessary, you can use the "dynamic" keyword so that the arrays point to the same reference. - Arrays: protected access to elements passed as parameters to a procedure
This option is used to protect an array element passed to a procedure as a parameter. This allows you to modify, delete or add elements into the array from this procedure.
Note: When enabled, this option may slow down access to the array. - Optimization: enable inline expansion: This option speeds up code execution. Whenever possible, the compiler automatically replaces the procedure call with its code. This may result in an overall increase in code size, but faster procedure calls.
- "Data source names":
- "Variable name":
"Data source" variables create a data source that use the name of the variable. This may cause a problem in the following cases: - using arrays of data sources
- using data sources as class members.
- when two windows use the same Data Source variable.
- "Automatic name":
"Data Source" variables use a unique name for the data source. Please note quotation marks must be removed to manipulate the data source. Don't write:
M1 is Data Source
HReadFirst("M1") M1 is Data Source
HReadFirst(M1) - "Automatic name with references":
"Data Source" variables use a unique name for the data source. It is now possible to reference an existing data source, for example using the following syntax:
x is Data Source
x = FileName
x = QueryName
 The "Automatic name with references" option is not available.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|