2022.2

Parameters:
Name
Name of the field or attribute contained in each sub-node whose value will be used as the first sort cri-
teria. If it is an attribute instead of a field, this needs to be specified in the Flags parameter.
Flags (optional)
Set of flags that modify how the sorting on Name is done.
Name2 (optional)
Name of the field or attribute contained in each sub-node whose value will be used as the second sort
criteria. If it is an attribute instead of a field, this needs to be specified in the Flags2 parameter.
Flags2 (optional)
Set of flags that modify how the sorting on Name2 is done.
Name3 (optional)
Name of the field or attribute contained in each sub-node whose value will be used as the third sort cri-
teria. If it is an attribute instead of a field, this needs to be specified in the Flags3 parameter.
Flags3 (optional)
Set of flags that modify how the sorting on Name3 is done.
Exceptions:
l
EOleException: Specified field or attribute does not exist in one of the sub-nodes.
l
EOleException: A numeric sort is specified and one of the fields or attributes does not contain a
valid numeric integer value.
l
EOleException: An error occurred while comparing two strings.
Attributes
An Attribute is a read-only, system-defined element: a name/value pair, where the name is case-
insensitive. It holds certain information about a certain "Node" on page172 in the Metadata structure.
This information can be static (e.g. the size of a physical page) or evaluated on-the-fly (e.g. the number
of documents in a group).
Attributes are non-repetitive (i.e. name is unique) and do not persist through Metadata recreation.
For an overview of Attributes and the Node types in which they are available, see the "Metadata Attrib-
utes reference" on page73.
Attributes are stored in a collection container object, just like the Node's "Fields" on the facing page. As
is the case with the different types of Nodes, both collections share a number of methods and prop-
Page 184