At 08:59 PM 08-06-01 +1200, you wrote:

>Not a feasable solution with literally thousands of filters assigned
>everywhere. Besides the problme is the null. If a field is left null, its
>order in the search is not teh same as blank or 0.
>
>Using a statement such as (xx > 0) fails to find them and so does (xx<=
>0).... it is illogical. It should be in one or the other set.
>Unfortunately the defaults in Interbase do not work when using IBO.
>
>IBO should save '' and 0 for nulls in strings and integers.

No way! The realisation layers between the abstract data and the user should provide the capability to do what is needed - and they do. Zero is not the same as null, nor even comparable - as null reflects a data state ("unknown") while zero or emptystring reflect values.

IBO gives you the capability to save default values for any column. That is what IBO *should* do - not arbitrarily override abstract facts about data.

The database itself also allows you to force a value to be inserted if that is what your requirements demand. That is what NOT NULL and DEFAULT constraints are for.

Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________