In the application, some specific database information is displayed in the form of a restricted selection list: Yes / No, Round codes, Report groups, etc. These all correspond to tables that hold the limited list of items available for selection.

These datasets are called Local menus and are identified by a Chapter number, which is assigned to the corresponding table of available items. When a field in the database is linked to this type of data, the rank (row) number is actually recorded in the corresponding table. For instance, Local menu number 1 contains the two choices No and Yes (in this order): what is actually sorted in the database is '1' for the value No, and '2' for the value Yes.

A large number of local menus is used in the software. As with Miscellaneous tables, this system is used to avoid the creation of a large number of annex tables: the description of these local menus is stored in a single table in the database (table APLSTD). These local menus can be translated: as only the rank number is stored in the table, you only need to change your connection language to display or enter the table in this language.

When modifying these tables, make sure not to insert values but only add values at the end of the list. Inserting a value will move down all the following values and cause inconsistencies as only the row number is stored (unless no data has been assigned yet to the local menu). For example, if you enter Maybe on the first row of the No / Yes table, all the fields in the database set to Yes will be now set to No, and the ones set to No will display the value Maybe! The number of choices in a local menu is limited to 123.

Besides 'Local menus', some chapters in the table are used to store other messages, such as error messages. As a standard, when a specific message needs to be displayed to the user (for instance, a confirmation request, an error message, a comment in a log file, etc.), the message is stored in a chapter dedicated for that purpose, in order to make these messages translatable based on the connection language.

All the developers of specific functions are advised to follow this same process. To get easy access to the text in processes or calculation formula, the standard function mess provides access to the messages. Use mess(NUM,CHAP,1) to get access, in the current connection language, to the message number NUM coming from chapter CHAP.

As a general rule, all adonix technology softwares define their own chapter mapping by allocating number ranges to the functional modules for each product. Please refer to the appendix to know more about the assigned modules for each product.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

The entry is performed by chapter on a single tab. A chapter can be a local menu or even a group of messages. On exiting this function, if at least one local menu has been modified, the system will automatically launch an update of the local menus in order to update sequential files, used as caches for the local workstations depending on the languages managed in the folder.

Reports

By default, the following reports are associated with this function :

  PRTSCR : Screen print

  APLSTD : Local menus

This can be changed using a different setup.

Specific Buttons