Data Types
This function is used to define the data types that can be used in all the dictionaries where the data is defined: screen fields, table fields, report parameters...
A certain number of characteristics(internal type, length, actions...) are attached to a type to be automatically assigned to the fields using this type. It is not however necessary to define all the characteristics of a type. Indeed, the non-defined characteristics at the type level will be requested at the definition of the screen, which makes it possible to define the generic types. ADONIX delivers a certain number of data types containing only the internal type, that is to say the field storage type. These data types cannot be modified. Here is the list:
Type code | Definition |
A | Alphanumeric string |
ABB | Blob |
ACB | Clob |
C | Short integer |
D | Date |
DCB | Decimal amount |
L | Long integer |
M | Local menu |
MM | Local menu with the possibility to filter the elements |
M or MM corresponding to a local menu where the number is given by the contents of the Menu column in the table or screen dictionary. A local menu is a title table, entered either in the form of a combi box or in the form of radio buttons in the form of a check box (if it is local menu 1, which contains the values Yes/No). In the database only the choice number is stored in the list (0 if the field is not assigned, 1 if the first title in the list is selected and so on).
In the table shown below are displayed the data types corresponding to the supervisor technical elements:
Type code | Definition |
ABS | Variable at the bottom of the grid |
AT | Field indicating the blob type |
AX1 | Translated text (length 12) |
AX2 | Translated text (length 20) |
AX3 | Translated text (length 30) |
W | Filler |
ABSidentifies the screen field at the bottom of the grid. This field is mandatory for all the grid section defined in a screen. If the grid will accept entries, this field will be in entry mode; if the grid is hidden, this field will be in hidden mode.
W identifies a filler. This data type placed in a screen field will leave a space between the previous field and the next field, if theses two fields are on the same line. It is however preferable to use, to this end, the column section in the screen dictionary and to only use the fields with the data type W as a last resort.
AX1, AX2, AX3 identify the translated texts. In fact, this field is not created in the database. Its field name serves to identify the translated text that will be stored in the dedicated table ATEXTRA.
Displayed in the table below is a list of the functional type that are particularly important (this list is not exhaustive):
Type code | Definition |
MD1 to MD4 | Formats for the amounts depending on the currency (which must be on-line): the 4 corresponding formats are defined in the currency table. |
MC1 to MC4 | Formats for the amounts depending on the currency: These are the same types as above, but they are optimised for use in a scrolling grid in which a column is entered with a currency that does not depend on the current line. |
MS1 to MS4 | Amounts in the site currency |
ADI | Code stored in a miscellaneous table (where the number is given in the table dictionary, by the link expression). |
HM | Hour: minute |
QTY | Quantity |
QT1 to QT5 | Optimised quantity for the grid section (same notes as above: the format of a column must not depend on the current line) |
Prerequisite
Refer to documentation Implementation
Screen management
Header
Fields
The following fields are present on this tab :
|
|
|
|
Close
Tab General
Fields
The following fields are present on this tab :
Characteristics
|
|
|
|
Type
|
|
|
|
|
|
Format
|
|
|
|
Close
Tab Convergence
Fields
The following fields are included in this window :
Object
| Used to indicate if necessary, the object associated with the data type. The linked table managed by the object is displayed. The presence of an object code automatically starts:
|
|
|
Format
| Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.
|
|
|
|
|
| Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.
|
| This field allows you to enter a calculation formula to assign a default value to fields of this type An example can be seen in the CRY type, which defines the country code : the GPAYS variable, which defines the local country, is proposed as the default value for all the fields of this type. This default value is automatically proposed in the screen fields using this type of data. However, if a field using this data type has its own default value in the screen, it's this that will be used; in this case, the default value for the data type is ignored. |
Grid Actions
| This grid is used to declare the actions catalogued in the actions dictionary. The objective is that for all fields having this data type, the actions defined here will be systematically executed. If a single action is defined is defined for both the data type and the screen field, the actions will be executed consecutively and in the following order : it is the data type then the field. There is a particular case for the "selection" and "button" actions, for which only the screen field action will be executed. This grid makes it possible to define the particular actions associated with the field. The possible action types are :
|
| Indicate the actions to be carried out in a systematic manner on the type of data. |
| This field is used to define the context of the action execution :
|
Close
Tab Class
Fields
The following fields are included in this window :
Type
|
|
Details
|
|
|
|
|
|
|
|
|
|
Default representations
|
|
|
Grid Rules
|
|
|
|
|
|
|
|
|
|
|
|
Grid Parameters
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Close
Action icon
Reports
By default, the following reports are associated with this function :
ATYPE : Data type
This can be changed using a different setup.
Specific Buttons
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close This button is used to copy the data type definition to another folder. |
Menu Bar
Documentation / Paragraphs
This choice of menu allows to zoom to the documentation management, on the first documentation paragraph (if it exists) related to the current record.
Documentation / Links
This choice of menu allows to zoom on the dictionary link management function. This function allows to establish links between the current record and other records (for example links between functions and parameters). These links, dedicated for documentation purpose, allows the generation of documentation structure.
Documentation / Generation
This choice of menu allows to generate the documentation. Three types of generation can be separately or simultaneously started :
- the generation of the structure of documentation from dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
- the generation of the documentation itself from the previous table (they have been normally completed after the first generation).
- the field help documentation generation.
The ranges and parameter proposed by default are defaulted according ti the current record, but they can be changed during the execution.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Incorrect length
The length associated with a field is incompatible with the given internal data type.
Local menu not defined
The local menu number is incorrect
Invalid character
Incorrect characters have been entered in the format.
Incorrect format
The format that has been defined is invalid.
Incorrect option
The option associated with the format is invalid.
Data type not modifiable
The database data types are not modifiable. Example : "A","C","D","L","M","MM","DCB","AV","W","ACB","ABB".