##OV Tag

If your procedure contains complex SQL, it may not be parsed correctly. It is recommended that you first try to parse the SQL using SQLHelp to see if any issues are present before using the override tag.

Common issues include:

Use of dynamic column names. A dynamic column name is one built from the result set. (e.g. SELECT 'string' + table.Name FROM table)
Use of multiple paths of execution. If a conditional expression returns a result set, the parser will assume it to be present under all situations. i.e. the parser does not evaluate the potential paths of execution. The net result is the appearance of additional result sets.
Selecting values into a return value. The return values parsed from the SQL procedure are static values. The parser makes no attempt to parse dynamic values.
Result sets returned as the result of an EXECUTE on additional procedures.

If the ##OV tag is present, neither the return values, nor the result sets will be parsed. If you use the ##OV tag, incorrect results may be obtained unless the ##RD, ##RS, ##MD, ##CU and ##TR tags are kept in sync with changes to the procedures.

You can also set the entire project as being overridden. This eliminates the need to enter ##OV on each batch during design time.

To reverse the effect of the override tag, either remove it from the batch, of use the ##NOV tag.

Syntax

-- ##OV