J
JH Szymanski
I am programming an Access Project (.adp) and have noticed
inconsistent behavior from the filter properties. For
example, .Filter = "Like Z" for a Form returns all values
that start with "Z". However, the same filter applied to
a Report on the same data source will only match those
values equal to "Z". It looks like the Report filter (and
DCount) are honoring the T-SQL documented behavior of
Like, while the Form's filter is adding some undocumented
matching. (It's treating it as Like 'Z%'.) Also, some
aspects of the .adp work with the old Access '*' wildcard
syntax, while others seem to work only with the T-SQL '%'
syntax.
Can anyone confirm this quirky behavior? Is it
documented? If so, is there a kludge to work around it
and get consistent behavior? Can the implicit use of '*'
wildcards be disabled so that T-SQL '%' must be used?
inconsistent behavior from the filter properties. For
example, .Filter = "Like Z" for a Form returns all values
that start with "Z". However, the same filter applied to
a Report on the same data source will only match those
values equal to "Z". It looks like the Report filter (and
DCount) are honoring the T-SQL documented behavior of
Like, while the Form's filter is adding some undocumented
matching. (It's treating it as Like 'Z%'.) Also, some
aspects of the .adp work with the old Access '*' wildcard
syntax, while others seem to work only with the T-SQL '%'
syntax.
Can anyone confirm this quirky behavior? Is it
documented? If so, is there a kludge to work around it
and get consistent behavior? Can the implicit use of '*'
wildcards be disabled so that T-SQL '%' must be used?