First I should mention that I have "treat blanks as zero" ticked in settings of Pdx10 running on Win7 at work. On my report I have numeric fields which are covered by undefined calculated fields that show a text value of "Absent" when the corresponding numeric value is 0.0. Otherwise the numeric value is shown. The problem is that when the field is left blank, I want a calculated field to show "Not Done". When I set up an iif isBlank() condition in a calculated field, the calculation treats the blank field as a 0 and reports 0.0 rather than "Not Done". It is as if the treat blank as zero over-rides the isBlank() request.... This does not seem right to me because the underlying table value certainly is blank... Can you help? Regards. Paul
If you think about it this is correct behavior. If you were attempting a simple calculation such as 100- you would want to "Treat blanks as 0". Unfortunately, we cant have it both ways.
You may have to do something a little more arcane such has having an un-displayed field attached to the field that has objectpal code to either assign the current table value to the unassigned field or if the field value is Blank then assign Not Done.
I have an unassigned field on the report which is defined as a calculated field and in the calculation references the (blank) table field via the alias and the field name... I would have thought that the reference to the table field with alias would return an isblank() = True rather than a zero.
Paradox
Print This
