Hello,

I'm building a 'search-order'-screen with a couple of search elements like OrderDate (DateEdit). I have bounded the DateEdit.EditValue to a FieldCompareValuePredicate's value property. This predicate is added to a general filter in the constructor of the screen. In this way the only thing I have to do when the 'search'-button is pressed is do a GetMulti() with the general filter as parameter. This works fine only if the value of the DateEdit != null. Is that correct behaviour? Or do I have to check if the value != null and exclude the predicate from the general filter?

Greetz,

zaad

I think you should exclude the predicate from the filter if the value is null, unless you want to search for null values in the database, then you should use the "FieldCompareNullPredicate" instead of the "FieldCompareValuePredicate"