The default is "OK Default Condition (Return Code is 0). I have a dozen Data Flows and sometimes I'll receive a Return Code = 18708 because nothing matched the filter. The process stops and the chain is broken. When this occurs, I need the flow to update the rerst of the tables. I can change the condition type to Unconditional so the Flow doesn't stop or I can code a Custom condition. I'm afraid if I select Unconditional, execution may pass to next flow when it shouldn't.
What are your thoughts?
I think you usually get RC 18708 when there are no records returned from your query. In version 7.1.3 if you look at the flow properties and uncheck "Stop processing if 0 rows are selected", this return code goes away and the flow exits successfully (if 0 records are returned).
We'll be upgrading to 7.11 by year-end. I'll leave the connection as "unconditional" for now because that seems to be the only way I can get the Data Flow to proceed onto the next one if there are no records that match the filter.
Unix Solaris 5.8
DataBase - Oracle 9i2
|Powered by Social Strata|