Help / Editors / Data model editor / Logical Data Model
  • Overview
  • Creating a link
  • Notes
  • Owner file and member file
  • Referential integrity
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
The links are used to link the date files described in an analysis between themselves.
Several types of links are available. For more details, see Types of links.
Reminder: The "LDM" and "Analysis" terms are indifferently used to define the structure of database associated with a project.
Creating a link
To create a link:
  1. On the "Analysis" tab, in the "Creation" group, click "New link". The mouse cursor turns into a pen.
  2. Click the two data files that must be linked. The link description wizard opens automatically.
  3. To define the cardinalities between the two files:
    • select the desired cardinalities (0, 1; 1, 1; 0, N; 1, N).
    • answer the questions. The cardinalities will be automatically updated.
  4. To define the advanced cardinalities, check "Display advanced cardinalities" and answer the questions.
  5. Specify the link caption and briefly describe the purpose of the link. Go to the next step.
  6. Specify the keys to be linked. Go to the next step.
  7. Define the integrity rules. These rules ensure data integrity when one of the keys of the relationship is modified or deleted.
  8. Validate. The link is automatically created.
  • For more details on cardinalities, see Cardinalities.
  • If the data files to link contain an identical unique composite key (and also contain the items included in the composite key), a link can be performed on this composite key.

Owner file and member file

When there is a link between two data files, there is an owner file and a member file:
  • the owner file is the key owner.
  • the member file is a member of analysis files containing a copy of key.
To manage the link between two data files, the key of the owner file is copied to the member file.
For example, the key of the "Supplier" file is copied to each record of the "Product" file. Several records in the "Product" file can have the same key as the "Supplier" file:
  • the owner file is"Supplier",
  • the member file is "Product".
This type of link is represented as follows:

Referential integrity

Referential integrity in a database is a set of constraints that maintains consistency of data in a relationship between two data files.
Referential integrity checks that:
  • if a record is deleted from the owner file, the corresponding records are also deleted from the member files,
  • if a record is added to a member data file, there is a matching record in the owner data file,
  • if a record is modified in the owner file, the unique key is not modified,
  • ...
The referential integrity is checked based on the nature of the link between the data files.
Related Examples:
WD Reflexive link Training (WINDEV): WD Reflexive link
[ + ] This example presents the management of a reflexive link with the WLanguage functions.
The following topics are presented in this example:
1/ Fill a control with HFSQL content (automatic management of reflexive link).
2/ Fill by programming.
Minimum version required
  • Version 9
This page is also available for…
Click [Add] to post a comment

Last update: 06/22/2023

Send a report | Local help