These sublists are used to create and manage link relationships to and from the data class. More information: -> Relationships between data classes.
Link Name | name of a link between two data classes |
Table 1 | name of Table 1 |
Key 1 | name of the Key for Table 1 |
Table 2 | name of Table 2 |
Key 2 | name of the Key field in Table 2 |
>Check Value | controls deletion of records in Table 1 |
>Delete Flag | controls Table 2's behavior when records are deleted in Table 1 |
>Outer Join | outer join flag |
<Check Value | controls deletion of records in Table 2 |
<Delete Flag | controls Table 1's behavior when records are deleted in Table 2 |
<Outer Join | outer join flag |
Object Title | a relationship's title |
Comments | comments about the relationship record |
Form | opens the selected record in the Link Data form |
attribute | master attribute for link (T_CONSTRAINT) |
type, entry | string, entry required |
max. no. of characters | 20 |
selection tool | no |
multilingual field | no |
You can enter (or select from the menu) only existing database tables.
Key 1
attribute
master attribute for link (T_CONSTRAINT)
type, entry
string, entry required
max. no. of characters
255
selection tool
menu with all fields of the table 1
multilingual field
no
The key is used to uniquely identify records in Table 1 of the association.
Names of Key fields may contain spaces, and several fields can be selected as Key fields. DataView then generates a string of comma-separated field names. <<CLEAR >> in the selection tool deletes the list of Key fields.
Only indexed fields should be used as keys.
If you want to create an association between classes which are represented as DataView tables in the database, or which point to such classes, you can also use DataView's internal C_ID fields as keys.
Attention!
Multilingual and system fields may not be used as keys in relationships.
Table 2
You can enter (or select from the menu) only existing database tables.
Key 2
attribute
master attribute for link (T_CONSTRAINT)
type, entry
string, entry required
max. no. of characters
255
selection tool
menu with all fields of the table 2
multilingual field
no
The key is used to uniquely identify records in Table 2 of the relationship.
Names of Key fields may contain spaces, and several fields can be selected as Key fields. DataView then generates a string of comma-separated field names. <<CLEAR >> in the selection tool deletes the list of Key fields.
Only indexed fields should be used as keys.
If you want to create an association between classes which are represented as DataView tables in the database, or which point to such classes, you can also use DataView's internal C_ID fields as keys.
Attention!
Multilingual and system fields may not be used as keys in relationships.
>Check Value
attribute
master attribute for link (T_CONSTRAINT)
type, entry
Integer, entry required
max. no. of characters
3
selection tool
no
multilingual field
no
The Check Value determines when the user can delete a record from Table 1 which is linked to records in Table 2. If the number of linked records in Table 2 is smaller than the Check Value, the record can be deleted from Table 1.
More information:
-> Checking for dependent elements
>Delete Flag
attribute
master attribute for link (T_CONSTRAINT)
type, entry
string, entry required
max. no. of characters
1
selection tool
menu with possible actions
multilingual field
no
When master tables are linked to themselves (e.g. to display item or usage lists), entire structures could be deleted recursively. For safety's sake, DataView moves anything deleted recursively to the trash first.
More information:
-> Automatically deleting dependent elements
>Outer-Join
attribute
master attribute for link (T_CONSTRAINT)
type, entry
logic
max. no. of characters
3
selection tool
no
multilingual field
no
More information:
-> Controlling display with outer joins
<Check Value
attribute
master attribute for link (T_CONSTRAINT)
type, entry
Integer, entry required
max. no. of characters
3
selection tool
no
multilingual field
no
The Check Value determines when the user can delete a record from Table 2 which is linked to records in Table 1. If the number of linked records in Table 1 is smaller than the Check Value, the record can be deleted from Table 2.
More information:
-> Checking for dependent elements
<Delete Flag
attribute
master attribute for link (T_CONSTRAINT)
type, entry
string, entry required
max. no. of characters
1
selection tool
menu
multilingual field
no
When master tables are linked to themselves (e.g. to display item or usage lists), entire structures could be deleted recursively. For safety's sake, DataView moves anything deleted recursively to the trash first.
More information:
-> Automatically deleting dependent elements
<Outer-Join
attribute
master attribute for link (T_CONSTRAINT)
type, entry
logic
max. no. of characters
3
selection tool
no
multilingual field
no
More information:
-> Controlling display with outer joins
Object Title
attribute
master attribute for link (T_CONSTRAINT)
type, entry
string, entry optional
max. no. of characters
20
selection tool
no
multilingual field
yes
The title is used in error messages.
Note!
You should always give your objects a title. If you don't, error messages will only contain the object's key, and you won't be able to find the object in a Search mask.
Comments
attribute
master attribute for link (T_CONSTRAINT)
type, entry
string, entry optional
max. no. of characters
255
selection tool
no
multilingual field
no
Form