C
Chris Bailey
I've run into a problem with Outlook 2011 in regards to the new
conversations feature. Please check out the following image, which I
refer to below.
http://www.minidomo.com/outlook-conversations.jpg
In this image, you see two shots of the same 8 messages from this
person's Inbox. On the right is the list after doing a database
rebuild, and in that example everything shows correctly. (Excuse the
redactions of names and email addresses -- I don't want to violate
anyone's privacy here.) On the left is an example of what happens when
this problem crops up. As you can see by the lines I've drawn, if a
conversation appears, it will display the subject line of the message
directly ABOVE it. If you have a standalone message (not part of a
conversation), it displays the correct subject line.
I've had this problem happen twice on the same Mac but so far not on
the other four stations I have upgraded to Outlook 2011 (at least, no
one has reported it yet). Rebuilding the database fixes the problem
when it happens. Has anyone else seen this issue? I'm wondering if it's
a bug or something wrong with the specific database in question.
Many thanks,
Chris Bailey
Benton Harbor, Michigan
conversations feature. Please check out the following image, which I
refer to below.
http://www.minidomo.com/outlook-conversations.jpg
In this image, you see two shots of the same 8 messages from this
person's Inbox. On the right is the list after doing a database
rebuild, and in that example everything shows correctly. (Excuse the
redactions of names and email addresses -- I don't want to violate
anyone's privacy here.) On the left is an example of what happens when
this problem crops up. As you can see by the lines I've drawn, if a
conversation appears, it will display the subject line of the message
directly ABOVE it. If you have a standalone message (not part of a
conversation), it displays the correct subject line.
I've had this problem happen twice on the same Mac but so far not on
the other four stations I have upgraded to Outlook 2011 (at least, no
one has reported it yet). Rebuilding the database fixes the problem
when it happens. Has anyone else seen this issue? I'm wondering if it's
a bug or something wrong with the specific database in question.
Many thanks,
Chris Bailey
Benton Harbor, Michigan