Problem with conditonal formatting

[FrustratedAlso]

I have a reports with fields for weight, height, width diameter, and depth (all database fields). I have these fields conditionally set to highlight the field if it is null

Expression is IsNull([fieldname])

. all the fields work properly except height. Anyone else had this problem? Solution?

[CJ_London]

is height actually null? Perhaps it defaults to 0?

[ItsMe]

I do not understand what you are trying to accomplish but, FYI IsNull is a function and returns a value. It is a triple state Boolean that is returned. However, if it returns Null, it is because your argument is not a valid expression. Otherwise, the IsNull() function will return True or False.

[FrustratedAlso]

is height actually null? Perhaps it defaults to 0?

It is null, weight, width diameter and depth all function properly.

[FrustratedAlso]

I do not understand what you are trying to accomplish but, FYI IsNull is a function and returns a value. It is a triple state Boolean that is returned. However, if it returns Null, it is because your argument is not a valid expression. Otherwise, the IsNull() function will return True or False.

I understand what IsNull does and how it functions, it does the job for the weight, width diameter and depth fields. It is only the height field that does not produce the results.

[ItsMe]

Perhaps you are using the intrinsic conditional formatting and then deleted the control bound to your Height field. Replacing the control with a new one may not employ the conditional formatting. A similar thing may happen if you are using formatting in the VBA module and do not rebuild the Sub Procedure.

[CJ_London]

height is a reserved word, have you tried changing the name? (looks like your other fields do not use reserved words)

have you tried ... expression is... isnull([fieldname])=true

I presume you have changed 'fieldname' to 'height'

[ItsMe]

...height is a reserved word, have you tried changing the name?...

That was throwing me off when I was trying to understand post #1. I think the brackets should manage the reserved word thing though?? Testing with another name would be a good idea, don't get me wrong.

[June7]

I have encountered a situation where even bracketing a reserved word name did not help - weird and unexpected. I HAD to change the fieldname (or create an alias name in query and use that - memory a little fuzzy on exactly what I did).

[FrustratedAlso]

I have encountered a situation where even bracketing a reserved word name did not help - weird and unexpected. I HAD to change the fieldname (or create an alias name in query and use that - memory a little fuzzy on exactly what I did).

Changing the field name on properties for the field worked. changed field name to Hgt and left the field source height.

[ItsMe]

So it was the name of the control that threw the wrench in the works?

[FrustratedAlso]

So it was the name of the control that threw the wrench in the works?

Yes it was, filed under "things that make no sense"