🚀 go-pugleaf

> My record set object is dataset1. DB is MS-SQL server.
>
>     dataset1.Filter = "Age <= 18 AND (Age = NULL OR Age >= 30)" // First
Code
>
> This code doesn't work. But these codes work:
>
>     dataset1.Filter = "(Age = NULL OR Age >= 30)" // Second Code
>     dataset1.Filter = "Age <= 18 AND (Age = NULL AND Age >= 30)" // Third
Code
>
> Change is only OR on third code according to first code. I have changed OR
> to AND. (Condition is nonsensical, but that's not important) Second code
> works fine.
>
> What this does mean? Can not ADO analyze "(<Condition1> AND <Condition2>
> (<Condition3> OR <Condition4>)" style Filter?

Check the msdn for information on ADODB.Recordset Filter property.

As I recall it has some totaly strange restrictions on how the filter string
should
be formated... I didn't check it now but I think it was that it only allows
format
strings that look like this:

    ( A and B and C and ... ) or ( D and E and F and ... ) or ...

So it has to be groups of conditions separated by ORs and in each of those
groups
you can only have simple conditions (no ORs or ANDs) separated by ANDs...

My first guess would be that someone at MS didn't know how to make a simple
arithmetic expression parser at the time this code was written :-))) but
then again...
that's just way too unbelievable to be true... so my second guess would be
that
I'm overlooking something that's the real reason for this behavior... :-)

HTH,
    Jurko