Re: Filter error... but why?
- From: Mike Niemann <mniemann@xxxxxxxxxxxxx>
- Date: Wed, 24 Aug 2005 21:58:56 -0400
Viatcheslav,
Thank you for the info... hard to believe that ADO can have such a
major limitation... but apparently it does.
Regards, Mike Niemann
On Tue, 23 Aug 2005 22:49:54 +0400, "Viatcheslav V. Vassiliev"
<support@xxxxxxxxxxxxxxx> wrote:
>ADO does not support filters in form A AND (B OR C). Instead you should
>write (A AND B) OR (A AND C). This is from MSDN:
>
>There is no precedence between AND and OR. Clauses can be grouped within
>parentheses. However, you cannot group clauses joined by an OR and then join
>the group to another clause with an AND, like this:
>(LastName = 'Smith' OR LastName = 'Jones') AND FirstName = 'John'
>Instead, you would construct this filter as
>(LastName = 'Smith' AND FirstName = 'John') OR (LastName = 'Jones' AND
>FirstName = 'John')
>
>//------------------------------------------
>Regards,
>Vassiliev V. V.
>http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
>ADO.Net
>http://www.oledbdirect.com - The fastest way to access MS SQL Server,
>MS Jet (Access) and Interbase (through OLEDB)
>
>
>"Mike Niemann" <mniemann@xxxxxxxxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
>ÓÌÅÄÕÀÝÅÅ: news:430b447c@xxxxxxxxxxxxxxxxxxxxxxxxx
>> TDataset filtering... filter looks good, why the exception?
>>
>> Filter - ( ([LastName] like 'm%')) AND (IdNumber = '333-33-1111' or
>> IdNumber
>> = '333-33-1112' or IdNumber = '333-33-1113' or IdNumber = '333-33-1114' or
>> IdNumber = '333-33-1115')
>>
>> Exception - Arguments are of the wrong type, are out os acceptable range,
>> or
>> are in conflict with one another.
>>
>> Regards, Mike Niemann
>>
>>
>
.
- References:
- Filter error... but why?
- From: Mike Niemann
- Re: Filter error... but why?
- From: Viatcheslav V. Vassiliev
- Filter error... but why?
- Prev by Date: SQL syntax problem........
- Next by Date: Re: SQL error
- Previous by thread: Re: Filter error... but why?
- Next by thread: ODBC-ing my app
- Index(es):
Relevant Pages
|