Steve,

Try using NVL() function instead. Normally the presence of a
.NULL. in a calculation will result as .NULL. for an answer.

From the help file on Null:
"Having no explicitly assigned value. NULL is not equivalent
to zero or blank. A value of NULL is not considered to be
greater than, less than, different than, or equivalent to any
other value, including another value of NULL.

Null values are:
Equal to the absence of any value.
Different than zero, the empty string (""), or blank.
Propagated in calculations and most functions."

Normally I avoid nulls unless absolutely necessary. In
SQL outer joins I will normally use NVL().

-myron kirby-
==================================================
>Hi,
>
>In a joint view, I got null values.
>
>In the report I had a .null.+.null.+ a value but it shows nothing.
>The line below it is: .null. + 100 = 100 it works.
>
>As a work around, I had to put IIF() to return 0.
>
>Is there restriction/bug on adding nulls.
>
>I got version 5.0a.
>
>Steve
>Thanks in advance for your answers.