This section shows the options and explains the handling and configuration when using the value database. The "Options (database configuration)" dialogue is the main configuration tool for handling the value database. For ease of understanding, especially where dialogue options correlate with other software settings, some topics have been split into separate documents.
|
"Options (database configuration)" dialogue
In this document, the administrative section of the database options is explained. The document describes the general use of the options. The influence of the database options when using the "Read from Database" or "Part Selection Database" dialogues is subject of separate topics. Link to: Read from Database
Link to: Part Selection Database
|
English:PDF | German:PDF | |
|
Activation and use of additional data
The Q-DAS software supports a range of additional data. The use of additional data requires activation in the system settings and in the database itself. How to activate and use the additional data is part of a separate topic. Link to: System Configuration Intern
|
|||
|
Data Amendment Log
With the data amendment log enabled, any change to the data pool can be logged in the measured value database. This option is most commonly used in the FDA environment to accurately log and prove (evidence) changes. Link to: Data Amendment Log
|
|||
| Save drawing files to database Stored in directories, the graphics can be accessed by absolute or relative reference. Loss of graphic files or renaming of paths would result in a complete loss of the assignment. For this reason, the possibility has been created to store the test plans together with the assigned graphics in the same database. How to store individual graphics to value database is part of the "Embedding and Using Graphics" topic. Link to: Images in the Q-DAS Applications |
|||
| Overview of the database structure - "All parts" function The "All parts" function is used by administrators to list the contents of the database and provide a quick overview of the k-fields, i.e. parts, characteristics, measured values and additional data in the database. |
English:PDF | German:PDF | |
| Subordinate Test Plans (Parent-Child Structures) Test plans with a parent-child structure are used to pass the k-field information from a superordinate test plan (parent) to all subordinate test plans (children). The purpose and use of parent-child structures is part of a separate topic. Link to: Subordinate Test Plans (Parent-Child Structures) |
|||
| Synchronising local test plans with the central database Depending on the data flow and existing infrastructure, it may be necessary to keep test plans locally available for recording. However, in order to view the locally recorded data from different measuring stations, or to make it available for various users, it is necessary to transfer them to a central location. How to synchronise local test plans with the central database is part of a separate topic. Link to: Synchronisation of Local Test Plans with the Central Database |
