Model 574 Programmable Counting System (PCS)
208 - GSE Scale Systems
10 CLEAR DATABASE:
a. <ENTER> key alone:
The "CLEAR DBASE" command is used to delete the
entire stored database. Again, the warning message
"SURE? ?????" will be displayed and pressing the
<ENTER> key will proceed with the deletion. Every
row in the currently selected database is then deleted.
b. An entry followed by the <ENTER> key:
This form of the "CLEAR DBASE" command allows a
non-selected database to be deleted. Again, the warning
message "SURE? ?????" will be displayed and pressing
the <ENTER> key will proceed with the deletion of all
the rows in the database. This command will most often
be used in transaction applications where information
about every transaction is stored. Then at desired
intervals (such as the end of the day, week, or shift) all of
the stored data can be printed or downloaded to a
computer. Afterward, the entire database would
normally be deleted.
11 SET DATABASE:
a. <ENTER> key alone:
The "SET DBASE" command resets the current database
to be the first defined database. Up to 16 databases may
be defined within the 574. All database operations are
performed on the currently selected database. Therefore
it is necessary to first select the required database before
performing a series of operations on a specific database.
If only one database is used then the "SET DBASE"
commands will never need to be used.
b. An entry followed by the <ENTER> key:
Key in the number of the database (ie 1 through 16) to be
selected followed by the <ENTER> key. This sets the
current database accordingly and all subsequent database
commands will be performed on that database until
another "SET DBASE" command is issued.
Multiple databases may be used in many applications.
For example, one database may consist of the part
number, description, net weight on hand, amount on
order, etc ..., while a second database might consist of
transaction data for various part numbers, a third
database could contain purchase orders for various part
numbers along with quantites ordered and their due
dates. Other examples are provided in our application
examples to be porvided in the near future. If a database
is attempted to be selected which is not currently setup,
the error message "NOT SETUP" is displayed breifly.
12 SET COLUMN:
a. <ENTER> key alone:
The "Set Colmn" command is used to specify a column
to be the "KEY" column for the next database command.
Invoking this command without preceding it with a
column number causes the default (ie look-up) column to
be reset to the first column of the selected database. This
is automatically the case every time the unit is powered
up and every time the indicator is re-initialized by
exitting the setup mode and saving changes.
b. An entry followed by the <ENTER> key:
The entry preceding the <ENTER> key must be the
parameter ID of one of the columns for the selected
DATABASE. The specified column has no immediate
effect but will affect the next database command, if it is
depedent on the selected column. Normally the selected
column will default back to the first column after the first
database command is issued. However, if the entry starts
with a decimal point then the newly selected key column
will remain in effect until the "SET COLMN" command
is issued again. However if another DATABASE is
selected, if that DATABASE does not include the
currently selected column's parameter ID then the key
column is reset to the first column. Also, if the unit is re-
initialized then the selected column is reset to the first
column of the first DATABASE which has been setup.
For example, keying [.23] [ENTER] will semi-
permanently set the key field for the selected
DATABASE to be the column whose parameter ID is 23,
ie ID #3.
The "SET COLMN" command can be used to recall a
row from memory based on information stored in a
column other than the first column. Generally databases
should be setup to have the first column be the column
which would normally be searched through. However
some applications require that a search be performed on
other columns during certain special operations. One
such example is attempting to determine a part number
when only the description is known. Another example is
searching through a transaction database (whose first
column is part number) for a specific account number.
13 DOWNLOAD:
To Next Page
Loading...