P
Paul Reiners
We've been running into the following bug. We have a program that
uses the Outlook and the CDO COM interfaces. It does most things
through the Outlook interface, but it does a few things through the
CDO interface, and it maintains both the Outlook NameSpace and the CDO
Session connections open continuously. But, I believe most of the
operations in the scenario below are done through the Outlook
interface.
Scenario:
1. Program logs in to Outlook using Profile A.
2. Program creates a TaskItem. User B (a person, not a program) has
access to this TaskItem through his own profile, Profile B.
3. User B logs in to Outlook using Profile B.
4. User B modifies the TaskItem. (For example, he could add something
to the Body of the TaskItem.)
5. Program retrieves the TaskItem and reads its property values. Note
that the Program has been continuously logged in to Outlook since Step
1. Program does not see the changed property values from Step 4.
Has anyone seen problems similar to this?
uses the Outlook and the CDO COM interfaces. It does most things
through the Outlook interface, but it does a few things through the
CDO interface, and it maintains both the Outlook NameSpace and the CDO
Session connections open continuously. But, I believe most of the
operations in the scenario below are done through the Outlook
interface.
Scenario:
1. Program logs in to Outlook using Profile A.
2. Program creates a TaskItem. User B (a person, not a program) has
access to this TaskItem through his own profile, Profile B.
3. User B logs in to Outlook using Profile B.
4. User B modifies the TaskItem. (For example, he could add something
to the Body of the TaskItem.)
5. Program retrieves the TaskItem and reads its property values. Note
that the Program has been continuously logged in to Outlook since Step
1. Program does not see the changed property values from Step 4.
Has anyone seen problems similar to this?