With all due respect, the quickest way to ensure that you'll never find an
answer to any problem is to approach it on the basis of a foregone
conclusion "outlook caused it" with no fsupporting facts particularly when
combined with an extremely biased and subjective "negative" viewpoint. I
also seriously doubt this to be an issue caused by Outlook "itself" for all
kinds of reasons.
This is what IS known from the information you provided:
#1 - The inbox folder is contained in a "data file" which can be accessed
by any program totally independant of Outlook (the program)
#2 - Whatever is occuring is common to your environment since 2 people
evidently have encountered the same issue within what "sounds like" to be
the same very short period of time
(there also seems to be a definite lack of any one else reporting
anything similar which one would expect to see for a "generic" problem)
This is what is NOT known:
#1 - Your Outlook version and SP level
#2 - Your operating system with SP level
#3 - Version of NOD software
#4 - Version of BlackBerry software
#5 - Any addins aside from those mentioned that may or may not be installed
#6 - Whether this involves a PST or Exchange based mailbox
#7 - What is common in your environment for the 2 users who have
encountered the same issue?
#8 - What exactly occured on these systems "when" this issue surfaced? Was
it not immediately noticed?
#9 - Did both users happen to recieve/open the same email message (with or
without an attachment?)
#10 - Is image001.jpg a filename that was attached to any email message?
#11 - Are both users "identically" configured with the exact same versions
of ALL software?
(just to start the list of questions that "should be" asked by a "support"
desk before proclaiming "the program responsible")
The statement "Any properly programmed software would prevent such broken
functionality" is the equivalent of saying that "it is any car
manufacturer's fault
when one of their vehicles doesn't run properly because the driver put
<water and sugar> into the gas tank instead of gas".
You could also apply that same logic and blame Microsoft for the recent
McAfee fiasco that brought down countless systems because Microsoft didn't
anticipate every conceivable issue in the world that could be caused by
some other product. This is not "blindly" defending Microsoft - just
applying
reason and logic to a specific issue at hand.
Karl
--
____________________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - QuickPort/DataPort/Exporter/Toolkit/Duplicate Contact Mgr
"Contact import/export/data management tools for Outlook '2000/2010"
http://www.contactgenie.com