This content has been marked as final. Show 3 replies
I confirm this strange behavior in AG10 sp4.
Moreover, this same happens when Definition Query is set (eg. "A_strings" <> '1A' ) - besides the excluded value, all records with NULLs are excluded.
In your case, when you want to preserve NULLs, you can try:
"qualifier" IS NOT NULL
Thanks m.gasior :-)
That works with a definition query, but not with quantity symbol classification using exclusions. For now, I populated all <null> values in [qualifier] with a "-" but in a table that looks like it means something. <null> indicates that the [result] is valid, so if there's anything in the [qualifier] field, that is a flag that alerts the user to a potential problem with the result.
Is there an environment setting to handle null values this way? If not, can ESRI make this available soon? There are many other instances where this has been a problem for me.
... a thought: I could change the "-" to a " " (space) so it looks blank to the user & not get tossed out as <null>...