Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Selection Formula Help

Status
Not open for further replies.

TEM3

Technical User
Dec 6, 2004
324
US
Using CR 8.5:

Not only is this selection formula ugly, the last three arguments are ignored -

{ARRESULT.Result} <> "0" or
{ARRESULT.Result} <> "" or
{ARRESULT.Result} <> "False" or
{ARRESULT.Result} <> "Not Performed" or
{ARRESULT.Result} <> "N/A" or
{ARRESULT.Result} <> "Not Applicable";

Is there better way (and a way that will test the last three statements)?
 
Not ({ARRESULT.Result}) in ["0","False","Not Performed","N/A","Not Applicable"]

This is case sensitive, so when you say that some arguments are being ignored, verify that your selection criteria addresses this.

Naith
 
That should be:

Not ({ARRESULT.Result} in ["0","False","Not Performed","N/A","Not Applicable"])
 
Thanks. It works fine. Question though..... How come this takes care of Null values in {ARRESULT.Result} too? Is that automatic??
 
No. :p

The only thing I can think of is that you must have Convert Database Null Values to Default checked on in your Options or Report Options, in the File Menu.

To handle nulls otherwise, you'd need to explicitly reference the IsNull function in your formula:

i.e.
Not IsNull({ARRESULT.Result}) and
Not ({ARRESULT.Result}) in ["0","False","Not Performed","N/A","Not Applicable"]

Naith
 
Yes I do (have Null Values set to default checked). Guess that put's something other than a Null there (like a "0" or something I am filtering for.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top