> I'll use > IF var1 <> .var2 OR (var1 is NOT NULL and var2 IS NULL) OR (var1 IS NULL and > var2 IS NOT NULL) THEN > A little longer to write, but no doubts that way.
My problem is that in this application (which I inherited -- just want to make that clear!) there are SELECTs using four comparisons, any two or three of which could possibly be NULL for a given run. To handle all the possible combinations, I would have to write very long and, more to the point, non-optimizable WHERE clauses. The ultimate solution is to find those columns that are causing the SET ZERO ON problems and default them to 0, which is the correct approach (I think). Then I could SET ZERO OFF, which ought to allow my IntCol = (.vMaybeNullVar) comparisons to work with EQNULL set ON. -- Larry
