Hi Bill

Thanks for the replies.  Sorry if I am confusing the issue.  What it comes down to is this:  If the stored proc fails due to a hard database error (@@error <>0) then the task should fail, that's the easy part.  I need to be able to capture business logic "soft" failures that are coded within the proc as well (stored proc return value <> 0).  An execute SQL task itself does not fail just because a stored proc returns a value other than zero.  That's why using the standard On Failure workflow won't work for me here. 

I like your idea about inserting some "junk sql" after the email is generated.  That should do the trick nicely.

Thanks again.