QlikView Reference Manual.pdf - QlikCommunity - QlikView

Force
The force statement forces QlikView to interpret field values of subsequent Load (page 246) and Select
(SQL) (page 262) statements as written with only upper case letters, with only lower case letters, as always
capitalized or as they appear (mixed). This statement makes it possible to associate field values from tables
made according to different conventions.
The syntax is:
force ( capitalization | case upper | case lower | case mixed )
Examples:
Force Capitalization;
Force Case Upper;
Force Case Lower;
Force Case Mixed;
If nothing is specified, force case mixed is assumed. The force statement is valid until a new force statement
is made.
The force statement has no effect in the access section: all field values loaded are case insensitive.
Back to Script Statements and Keywords (page 219).
Generic
The unpacking and loading of a generic database can be done with a generic prefix. For a description of a
generic database, see chapter Generic Database in section Evaluating the Loaded Data (page 375).
The syntax is:
generic( loadstatement | selectstatement )
Examples:
Generic Load * from abc.csv;
Generic Select * from table1;
Back to Script Statements and Keywords (page 219).
Hierarchy
The hierarchy keyword is a prefix to the Load (page 246) and Select (SQL) (page 262) statements. It is
used to transform an adjacent nodes table to an expanded nodes table. Hence, the internal table must be an
adjacent nodes table. The output of the hierarchy prefix is an expanded nodes table with all the needed
additional fields.
Adjacent nodes tables are tables where each record corresponds to a node and has a field that contains a reference
to the parent node. In such a table the node is stored on one record only but can still have any
number of children. The table may of course contain additional fields describing attributes for the nodes.
In expanded nodes tables each level in the hierarchy is stored in a separate field. The levels in an expanded
nodes table can easily be used e.g. in a pivot table or a in a tree structure. More details about adjacent nodes
tables and expanded nodes tables can be found in the chapter Hierarchies in section Evaluating the Loaded
Data (page 375).
Normally the internal table has exactly one record per node and in such a case the output table will contain
the same number of records. However, sometimes there are nodes with multiple parents, i.e. one node is represented
by several records. If so, the output table may have more records than the internal table.
236