I'm running into a problem on a system running Windows 2000 Server and Exchange Server 2000, where we import appointments from Outlook. If the Outlook account is populated with contacts, appointments, tasks, etc., and then all of the items are deleted, and the DeletedItems folder emptied, when we import the Appointments oItem.FindNext() no longer returns a NULL when it hits the end of the list, but instead returns the first item again. Here's pseudo code for what we have ...

lcFilter = (our criteria)
oItem = oCalendarList.Find(lcFilter)
Do While !isNull(oItem)
.
.
.
oItem = oCalendarList.FindNext()
EndDo

Based on all the MS documentation, once the FindNext() calls have gone through the entire list of items satisfying the filter criteria, FindNext SHOULD return a NULL, indicating "I'm Done!". However, on the Win2kServer/Exchange2000 system, once we delete ALL items, and then add a new Contact item with a Birthday or Anniversary, this no longer works; instead, after passing through the entire list, FindNext() does not return a NULL -- it returns the first item in the list.

A couple of questions ...

1 -- Has anyone else seen this behavior? Is this an endemic problem ... or de we just have a bad Outlook/Exchange?

2 -- Is there a way to "repair" the Exchange InformationStore?

Any help would be immensely appreciated -- I've been tearing mey hair out over this!