After daylight-saving time starts, Advanced Find may not return records that were created before that date in Microsoft CRM and in Microsoft CRM Sales for Outlook

When a record is created before daylight-saving time starts, Advanced Find in Microsoft Business Solutions CRM does not retrieve that record when the following conditions are true:

• You use the Created On box to perform the search.
• The search is performed after daylight-saving time has started.

For example, assume that the following conditions are true:

• Today's date is October 27, 2004 (10-27-04).
• Daylight-saving time started on October 24, 2004 (10-24-04).
• You created several contacts in Microsoft CRM on October 22, 2004 (10-22-04).

Additionally, assume that you follow these steps:

1. In Microsoft CRM, click Tools, and then click Advanced Find.
2. In the Created On box, type 10-22-04.
3. Click Search for Contacts.

The contacts that you created on the date that you specified, October 22, 2004, are not displayed.

Note If you use the Created On box in the Advanced Find dialog box to search for contacts, the results will be returned correctly for the following searches:

• For contacts that were created on a date that is the same as the date when daylight-saving time started
• For contacts that were created on a date that follows the date when daylight-saving time started

This issue also occurs in Microsoft Business Solutions CRM Sales for Outlook. For example, assume that the following conditions are true:

• Today's date is October 27, 2004 (10-27-04).
• Daylight-saving time started on October 24, 2004 (10-24-04).
• You created several contacts in Microsoft CRM Sales for Outlook on October 23, 2004 (10-23-04).

Additionally, assume that you follow these steps:

1. While you are online, on the Main Contacts screen, click Tools, and then click Advanced Find.
2. In the Created On box, type 10-23-04.
3. Click Search for Contacts.

The contacts that you created on the date that you specified, October 23, 2004, are not displayed.

Microsoft CRM has a fix for this problem that is part of a cumulative update. The cumulative update information is described in the following Microsoft Knowledge Base article: