You're welcome.

>Thank you for your response. I discovered the same and also discovered the reason why it worked in SQL Server 2005 was because the database, even though from the same client, it hadn't been converted yet (the database originally had no FK constraints so I had to update all empty FK fields with NULL once the FK constraints were applied). Once I updated the 2005 database the same as I had the 2000 database, the same behavior was also seen in 2005. I don't remember encountering this behavior before, but then again, I probably have and wrote the statement the second way and didn't think twice about it. I think this was a case of wondering if a word is spelled correctly, even though it is, sometimes it just don't look like it. Strange how you mind can play tricks on you sometimes.
>
>Thanks again for the response, Sergey. Must appreciated.
>
>James
>
>
>
>>From BOL 2005 for IN
>>Caution:
>>Any null values returned by subquery or expression that are compared to test_expression using IN or NOT IN return UNKNOWN. Using null values in together with IN or NOT IN can produce unexpected results.