T
traycerb
On XPsp2 trying to filter my Outlook 2003 (SP3) contacts (from within the
Outlook UI), I came across a curious behavior: Say I want filter to my
Contacts. I go to View|Arrange By|Current View|Customize Current
View|Filter|Advanced and set the Field to "Home Phone" and the Condition to
"Is Not Empty." Outcome: I get a (filtered) list of only those contacts who
have a non-empty "Home Phone" field, ie all people with Home Phones. Fine so
far, right?? Well...
Now If I click on the SQL tab (instead of the Advanced tab), it converts
that filter into SQL DASL form like so: NOT("urn:schemas:contacts:homePhone"
IS NULL). HOWEVER, when *that* filter is run, it gives a *different* set of
results, including some entries with empty "Home Phone" fields! This, despite
the fact that the filter was not changed, simply programatically converted
(by Outlook) to an SQL query. The results don't make sense either (it's not
the complete list of null "home phone" entries, it's not a concatenation of
the null+non-null).
Anyone have any idea what's up? The reason I need to use the SQL filter in
the first place is to create a more complex search than the one in the
Advanced tab allows.
I have a work-around which involves searching for a hyphen (which is
imperfect, as, depending on how the number was entered, not all phone numbers
will have hyphens), but I'd like to know if anyone else has this problem, or
has a real solution.
Outlook UI), I came across a curious behavior: Say I want filter to my
Contacts. I go to View|Arrange By|Current View|Customize Current
View|Filter|Advanced and set the Field to "Home Phone" and the Condition to
"Is Not Empty." Outcome: I get a (filtered) list of only those contacts who
have a non-empty "Home Phone" field, ie all people with Home Phones. Fine so
far, right?? Well...
Now If I click on the SQL tab (instead of the Advanced tab), it converts
that filter into SQL DASL form like so: NOT("urn:schemas:contacts:homePhone"
IS NULL). HOWEVER, when *that* filter is run, it gives a *different* set of
results, including some entries with empty "Home Phone" fields! This, despite
the fact that the filter was not changed, simply programatically converted
(by Outlook) to an SQL query. The results don't make sense either (it's not
the complete list of null "home phone" entries, it's not a concatenation of
the null+non-null).
Anyone have any idea what's up? The reason I need to use the SQL filter in
the first place is to create a more complex search than the one in the
Advanced tab allows.
I have a work-around which involves searching for a hyphen (which is
imperfect, as, depending on how the number was entered, not all phone numbers
will have hyphens), but I'd like to know if anyone else has this problem, or
has a real solution.