Instruction manual GLM-I Display and operating unit
38.019.129.001 en 75
7
7.6.3 Data for current production or saving into database
Depending on functional correlation and configuration of database you can decide during
saving if the data are to apply only for the current production or if they are to be saved also
into the database. Data together with article data that are saved into database
, are auto-
matically called up during article change.
Edited parameter tables saved into the database (e.g. label data) have
an effect on all articles to which the parameter table is allocated
.
It depends on the individual configuration of the database if savings to
the article database are made and in functional descriptions they can
only be taken into consideration as examples
. The constantly equal pro-
cedure is described in the following.
Table
When exiting a table and the option occurs to save it for current production or additional
saving into the database
, an inquiry occurs with the following possible answers:
<yes>: Save entries only for current production.
<Yes, also in database>: Save entries for current production and also into database.
<no>: Exit function without saving entries.
<Return> or <Cancel>: Return to function without saving the entries.
Input window
If a text or numeric entry can optionally be saved only either in the current production or
into the database, you can activate field "->Database [Etc]" or "Save in database" for addi-
tional saving.
7.7 Administrating tables and parameters
The following data can be edited in tables:
–
Article data, see page 131
– Label data, see page 200
– Autom. labeler data, see page 249
– Templates, see page 112
– Template cells, see page 114
– Static texts, see page 177
– Tendency regulation parameters, see page 455
– Package-specific scale parameters (only if device is configured as control scale)
– Weight classes, see page 310
– Code structure rules, see page 214
– Scanning rules, see page 240
To Next Page
Loading...
Need help?
General
