Using the AN D/ OR Operators By default, the AND operator will be used for all pairs of tests. You can use the <Tests> option to specify that if either one of a pair of tests is true, then the pair of tests is considered true. In the example above, the OR operator is added between the two tests. If either the BUDGET > 35000.00 AND BUDGET > 65000.00 test or the BUDGET > 35000.00 AND LEADER = '621-84-8911' test is true, the row of data is selected. KB_SQL evaluates conditions according to the IMPORTANT: SQL standards. For example, it applies the AND operator before it applies the OR operator. These operator precedence rules may not evaluate your SQL statements in the order that you want. If your query contains more than two tests or if you use both the AND and OR operators, it would be better to insert a calculation element with its Boolean logic. When you use calculation elements you can use parentheses to avoid any ambiguity. Refer to the section Using “ Calculation Elements for Complex Test Logic” for more information.
Using the AN D/ OR Operators By default, the AND operator will be used for all pairs of tests. You can use the <Tests> option to specify that if either one of a pair of tests is true, then the pair of tests is considered true. In the example above, the OR operator is added between the two tests. If either the BUDGET > 35000.00 AND BUDGET > 65000.00 test or the BUDGET > 35000.00 AND LEADER = '621-84-8911' test is true, the row of data is selected. IMPORTANT: KB_SQL evaluates conditions according to the SQL standards. For example, it applies the AND operator before it applies the OR operator. These operator precedence rules may not evaluate your SQL statements in the order that you want. If your query contains more than two tests or if you use both the AND and OR operators, it would be better to insert a calculation element with its Boolean logic. When you use calculation elements you can use parentheses to avoid any ambiguity. Refer to the section “ Using Calculation Elements for Complex Test Logic” for more information.
_new_ezq_reference.docx