As the email is stored in MSG format in a backend store, when Outlook
requests the properties we have to retrive the entire MSG with content and
properties in order just to process properties.

We have a shortened set of properties which is all that is needed to fill in
the current view stored off seperately which is all that is needed to fill
in the contents table.

My problem is that Outlook is presently requesting the properites and
opening the RTF property and the attachment table (as if some for of sync
event has happened).
So its not as if I could even hold off any longer as it does request all of
the above.)

My question is that this Outlook does not need to know this information
whilst in the UI any ideas what would make a request for it when you take
the focus away.
I started looking at the uuid in the entry id, the mdb provider etc. but
with no luck.

Any more ideas.

PS It is not normal behaviour as I see it, as it does not happen on the
wrapped PST I have, and also not on our most messageStore.
"Dmitry Streblechenko" wrote in message
...
I don't see why this is a problem. If Outlook wants it, let Outlook have
it.
Supposedly you already have data that you show in the folder contents
table, so you have some of it cached. Plus why not defer doing anything
time consuming until Outlook actually asks for the data via
IMessage::GetProps/OpenProperty/GetRecipientTable/GetAttachmentTable?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"T-rev" wrote in message
...
I have some strange behaviour across 2 very different releases of our
messageStore addin.
If the preview pane is turned off and you entry a folder, you get an
onSelectionChange for item clicked on in extensions and a request for the
EntryId from the Folder properties.

In a previous version of the software this is the same with the exception
that when you click off Outlook and highlight another window, it now
requests an openEntry on the IMessage itself, and we endup having to
build it all. I do not see any reason for this, as it does not need to
know the properties at this stage, and didn't for all of the UI
operations while still in Outlook (unless the message is opened)

Any Ideas???