Can you see that making a difference?
No. It looks like all you did was insert parentheses around the expressions combined with the OR operators. Since the OR operator has a lower associative precedence than <>, the parentheses are redundant.
Your earlier post is on the right track, testing each column value for a NULL value as well as performing the comparison and taking action accordingly.
You asked in that post if the code would execute correctly if there were no NULLs in the result set. I'm not sure you are using the term 'result set' correctly in the context of your question (since a 'result set' is the, er, result, of executing a SELECT query - we're talking about a WHERE predicate which is executed as the result set is being constructed), but the short answer is yes, if a column value is not null then the comparisons will be 'correct'.
But, given that you are using OUTER JOINs, there is no way to guarantee that the values will never be NULL. They will take on a NULL value if there is no corresponding row that satisfies the JOIN condition. If you know for certain there would always be a corresponding row, then there is no need for an OUTER JOIN; then an INNER JOIN would be preferable.
Custom Apps, Inc.