You will have to bite the bullet.  If you do a search of this site, you will find several threads that discuss this very issue.

This query would fail in SQL Server 2005 as well for the same reason it is failing in SQL Server 2000.

Actually, try this:

WHERE (OrderProcessed = @CaseFlag) or (@CaseFlag = 2)

Try this:

SELECT * FROM Orders

WHERE (OrderProcessed = CASE @CaseFlag WHEN 0 THEN 0

WHEN 1 THEN 1

END)

or (@CaseFlag = 2)

Sergiy,

Its do bad your only arguments are attacks on other peoples education, experience, and beliefs.  You would do better to provide specific facts and citiations to support your arguments rather than...

Actually, I am quite aware of the great range of mathematics, but even advanced mathematics is based on elementary (not school) principles.

And Achilles will over take the tortoise; its physics,...

Perhaps you should tell me if what they are saying at this link is true:

http://mathforum.org/dr.math/faq/faq.divideby0.html

No, Achilles will over take the tortoise.  But even then, you will never be wrong, right?

And again you are wrong.  n/0 = undefined, not infinity.  But then again, I'm sorry, you are never wrong, are you?

Wrong!

If 1/infinity = 0 then 1 = 0 * infinity which is wrong, as any grade school student will tell you that 0 * any number (0 * n )...

Just one objection Sergiy, 1/infinity <> 0.  It is extremely close, but isn't, so there is a possibility however slight that you can get a precise value.

Okay, added the column names, same problem.  As for draining the swamp, no.  I am seeing how this could be applied to find all new and changed records that need...

I am glad to here that things are running smoother and faster.  I have setup a sandbox with the data you provided, but I haven't had a chance yet to...

Hadn't heard that one.  Must have been before I joined the site.

The first example I gave you fails even with an order by in the statement.  Like I said, it appears to be a bit flaky and inconsistant.  I have used...