🚀 go-pugleaf

The Filter property in an ADO recordset must conform the restrictions set up
by ADO.  Go to http://msdn.microsoft.com/library/psdk/dasdk/mdap0i7m.htm for
details.

ADO doesn't support the IN function in a filter expression; only regualr
operators and LIKE.  Expressions that work in a BDE filter expression may
not work with ADO.  On a client-side cursor, a filter is not a "where
clause" because the filter is applied AFTER all the data has already been
retreived locally.  I'm not sure in server-side cursors perform filtering at
the server or locally, but in general it is more efficient when filtering to
use client-side cursors, which filter VERY fast.

Of course, you could also just add a "where clause" to your select
statement.

Mark Guerrieri
CTO
Creative Marketing Startegies
mguerrieri@cmsgrp.com



"Ray Parker" <rparker@madoff.com> wrote in message
news:3a7f0fe9$1_1@dnews...
> I have a TADOTable created from a view in and SQL7 server db, and I can't
> understand why a simple Filter (where clause) like "ID in (1)" doesn't
work.
> The exact string what I'm using is a legal 'where' clause, but when I set
> 'Filtered' to true, I get the error:
>
> "Arguments are of the wrong type, are out of acceptable range, or are in
> conflict with one another"
>
> Any ideas?
>
>