User defined fields in Outlook 2003

[Dave F]

I've set up 2 User Defined fields in Outlook 2003 -- Join Date and Renew
Date. Both fields are Date/Time types. I populate the Join Field with data
and some of the Renew Fields with data. The Renew field defaults to None if
not populated. The problem is when I sort on the Renew field, it doesn't
appear to sort properly, i.e. there are some "None" at the top, then some
dates, then more "None". Also, it doesn't filter correctly, i.e. when I
filter for Join Date on or before '12/01/05' and Renew Date "does not exist"
it doesn't return all the data it should. I created a new filter for
testing purposes, one with User Defined fields and one where the date field
was already set up, i.e Birthday. When I look at the SQL Filter
User Defined field
"http://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-000000000046}/Join%20Date"
<= '12/1/2005 12:00 AM'))
Standard Field "urn:schemas:contacts:bday" <= '12/1/2005 12:00 AM'

Why the difference? I'd like some help in understanding this.

Dave

 

[Sue Mosher [MVP-Outlook]]

The solution is to the Renew field on *all* items with data even if it's "None" -- which is actually the date #1/1/4501#.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Dave F]

Sue,
Thanks very much for your input. I think I understand what you are
suggesting. However, the Renew field is always populated with None. Then I
can populate it with a proper date. It still does not filter properly.
At the bottom of my original post, you will notice the SQL filter commands.
Can you explain the differences between the User Defined field filter that
begins with http:... and the Birthday field the begins with urn:? That's
what appears to be the key.

Dave F
The solution is to the Renew field on *all* items with data even if it's
"None" -- which is actually the date #1/1/4501#.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

The issues is that some items have never had a date set at all. Set a date for *all* items, and you should avoid the problem.

You cited schema property names for a custom property and a birthday. The birthday field exists on all items. The custom property only on those for which a value has been set.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers