Hello,

I have question about comparing numeric fields with null value. For
example:

SALARY<>0  returns rows with NULL values also

We use Oracle DB also and Oracle compare resutls with NULL are always
null (false). It's not problem in code. Programmers know what they are
do (sometimes , but some filter are edited by end users and they
don't want to think about DB used.

Is there any plan to (for example) add setting to enable to change
this behaviour ic code?

Thanks
Zdenek

Zdenek,

<< I have question about comparing numeric fields with null value. For
example:

SALARY<>0  returns rows with NULL values also

We use Oracle DB also and Oracle compare resutls with NULL are always null
(false). It's not problem in code. Programmers know what they are
do (sometimes , but some filter are edited by end users and they don't
want to think about DB used.

Is there any plan to (for example) add setting to enable to change this
behaviour ic code? >>

Unfortunately, no.  This is a "behavior" of DBISAM that is intrinsically
part of the core engine.

The workaround is to use:

SALARY <> 0 and SALARY IS NOT NULL

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Zdenek,
>
> << I have question about comparing numeric fields with null value.
> For example:
>
> SALARY<>0  returns rows with NULL values also
>
> We use Oracle DB also and Oracle compare resutls with NULL are always
> null (false). It's not problem in code. Programmers know what they
> are do (sometimes , but some filter are edited by end users and
> they don't want to think about DB used.
>
> Is there any plan to (for example) add setting to enable to change
> this behaviour ic code? >>
>
> Unfortunately, no.  This is a "behavior" of DBISAM that is
> intrinsically part of the core engine.
>
> The workaround is to use:
>
> SALARY <> 0 and SALARY IS NOT NULL

Ok. Thanks. No problem, finally.

PS: I know the workaround, but end users uses same filter against
Oracle and DBISAM and it produces another results.

--

"Zdenek Vasku" <z.vasku@ha-soft.cz> wrote in message
news:F16BBCE5-C703-4127-BE2A-6344E8C0FF47@news.elevatesoft.com...
>
> PS: I know the workaround, but end users uses same filter against
> Oracle and DBISAM and it produces another results.
>

Unless you have a specific reason for having null fields, make all amount
fields default to zero. Problem solved.

Robert