<0 matches blank fields...

[jasonwood]

I have a portal that I want to show records where field is less than 0 and not blank.

So I made a calculated global field which which always evaluates to 0, and a relationship to records with criteria: field < global

But I have learned that a blank field has a value (in relationships) that is lower than any entered value including negative numbers. What is the preferred way around this if I want to show related records that have a value <0 but not blank?

Would I just need to make a new global field with an extraordinarily negative number that the related field must always be greater than?

[Peter (duksis3)]

What happen if you change sign from "-" to "+" ?

[jasonwood]

what sign?

I'll rephrase:

if I set my global to 0, and tell my relationship to show me records where field is > my global, it works fine (showing records where field value is > 0. But if I tell my relationship to show me records where field is < my global, it shows me records where the field has a negative number (so far so good), and where it is blank (this is the problem - I don't want to see these).

So I adjusted my relationship to have 2 conditions - less than my global that is set to 0, and greater than my global that is set to -999999999999999... and that works great (since a blank field has an even lower value than -999999999999999) but I was wondering if that was the preferred method of doing this...

[Peter (duksis3)]

What about "AND"?

GlobalField=0

YourField

[comment]

You could define a calculation field in the child table =

Field < 0

and match it with a global (or unstored) calculation of 1.

[Søren Dyhr]

I have a portal that I want to show records where field is less than 0 and not blank.

No need for global field here - unless it's a user specific filtering!

--sd

filtering.zip