When a summary result of several fields, in a table,with numbers, is
used in a subsequent calc the result is as expected. (Summary + x =
answer)
If the summary is of a field that are all empty the result is OK the
summary is Zero and the calc returns the other value.(Summary + x = x)

If the summary is of a field where there are actually NO RECORDS, in
the table, then the result does not calculate at all even though the
other term has a value. (Summary + x = nothing )Just a blank field is
displayed

Is there an explanation or is that the way it is? :-?

--
John G.

In article <voOdnaAlt8SGoZ_SnZ2dnUVZ_rOdnZ2d (AT) westnet (DOT) com.au>, John G
<greentest (AT) ozemail (DOT) com.au> wrote:

I haven't got a version of FileMaker Pro in front of me, but there's an
option in the Define Calculation window to tell FileMaker what to do if
the source field(s) are empty - try turning that option on (or maybe it's
off, I can't recall which way around the option is worded).

The other option is to create this option yourself by checking for an
empty Summary field.
e.g.
Calc Calculation Field Number Result
= If (IsEmpty(Summary); X; Summary + X)

Helpful Harry )

Helpful Harry submitted this idea :
Thanks Harry,
I think I have tried every combination of the IF EMPTY check box but I
could have got it wrong.

I had thought of doing some check and you have saved me the trouble.
Your IF statement looks like the answer but I have not had time to
test it yet.

I should have said I am using FM P 11

--
John G.

In article <LOCdnQPWeM5WWZ_SnZ2dnUVZ_sWdnZ2d (AT) westnet (DOT) com.au>, John G
<greentest (AT) ozemail (DOT) com.au> wrote:
I have found that checkbox option to be rather buggy in every version of
FileMaker I've used (up to about verion 7 or 8), especially when defining
Auto-enter Calculations, which is why I usually ignore it and force my own
version within the calculation.

For example, if you have an auto-enter field that replies on a
user-entered field ... left to it's own options, FileMaker has a bad habit
of performing the auto-enter calculation even though the user-enter field
is still empty.
e.g.
If [IsEmpty(UserField); ""; {insert calculation}]
or
If [UserField=""; ""; {insert calculation}]

Testing the user-enter field yourself and forcing the the auto-enter field
to remain empty "encourages" FileMaker to calculate a proper result only
once the user-enter field actually has data in it.

Helpful Harry )