I agree, I ALWAYS have Eqnull set to off. But I have code like yours to compare old and new values, so I set it ON before the code, and set it OFF immediately afterwards.
Karen > Karen, > > Interesting thought but I refuse to futz with the EQNULL option. > It is not standard SQL and can have unwanted side effects. > Especially if this is a multi-user implementation. There were > several very interesting discussions of this subject several > years ago. I won't be using my original coding any time in the > near future. I am in the process of retrofitting the > alternative method into my other two databases with similar > requirements. >
