3-09:Enduser Selections Expression Option

Chapter 3-9: Query Processes

Enduser Selections Expression Option

The enduser selections expression option accesses the Enduser Selections Expression overlay, shown in Figure 3-9-6. Enduser Selections Expression specifications establish complex logical relationships between record selection criteria by using ANDs, ORs, NOTs, and parentheses. You define separate selections expressions for Enduser and Designer record selections. APPX ANDs these two selections expressions.

Figure 3-9-6. Enduser Selections Expression Overlay

The Enduser Selections Expression overlay contains two fields.

· Enduser Selections Expression defines a logical expression that joins record selection constraints established in the Enduser Selections overlay. Constraints are identified by their sequence number. They can then be combined with other constraints by using ANDs, ORs, and parentheses. Valid entries in a selections expression are any sequence number that a constraint is defined for, AND, OR, and ( ).

If Enduser Selections Expression is blank, all record selection constraints are ANDed. If either the Relation or the App/Field Name or Constant/Occ selections specification is blank, the relation is ignored (considered to be true). Any selections specification that is not explicitly referenced by a sequence number in a selections expression must be true for the selections expression to be true. A selections expression using all of the various Selections Expression entries might look something like the following:

((200 OR 300) AND 1000) OR (400 - 700)

· Editable at Runtime? indicates whether or not a user can change the selections expression during query setup. The default is “yes” but can be toggled to “no” by clicking the checkbox.

APPX Application Design Manual (01/13/03)