P
Paul Mateer
Hi, I've been working on a project involving a MAPI message store
provider and I've noticed some peculiar behaviour with Outlook 2003.
Specifically it seems that Outlook invokes the MSProviderInit()
function on three separate occasions, and I'd like to understand why.
The first two invocations occur directly after I access the message
store for the first time. The third occurs some (indeterminate) time
later (normally between 15 and 20 seconds after Outlook is launched).
What on earth is it doing? Why does Outlook 2003 require three
separate instances of a message store.
This functionality is causing me a problem as it means that multiple
instances of the same (supposedly) unique object are being created so
if Outlook is working with one and another piece of code updates the
other, it isn't reflected in Outlook.
As a potential solution, would there be any problem with forcing all
the calls to MSProviderInit to return the same unique object (rather
than three separate instances)?
Regards,
Paul Mateer
Meridio Ltd.
provider and I've noticed some peculiar behaviour with Outlook 2003.
Specifically it seems that Outlook invokes the MSProviderInit()
function on three separate occasions, and I'd like to understand why.
The first two invocations occur directly after I access the message
store for the first time. The third occurs some (indeterminate) time
later (normally between 15 and 20 seconds after Outlook is launched).
What on earth is it doing? Why does Outlook 2003 require three
separate instances of a message store.
This functionality is causing me a problem as it means that multiple
instances of the same (supposedly) unique object are being created so
if Outlook is working with one and another piece of code updates the
other, it isn't reflected in Outlook.
As a potential solution, would there be any problem with forcing all
the calls to MSProviderInit to return the same unique object (rather
than three separate instances)?
Regards,
Paul Mateer
Meridio Ltd.