Thanks Nick,

Actually, two clients called me yesterday and they both had a message saying that the value was not empty while it was showing 0.00 on the screen. When I tested it myself I found that empty(...) was giving me the wrong answer. As you, when I try it on the command windows, it works fine.

I fixed the problem by replacing the statement with ....<> 0.00 instead of using empty(...).

Very weird indeed. Maybe I'm due for long long vacations?