Have her check Task Manager to see if there is already an instance of
outlook.exe shown under the Processes tab. Could be she thought she had
exited Outlook but it failed to unload completely, a stub of code is still
in memory, and it interferes with subsequent loads of Outlook. This is not
a new problem. It is a really old problem that Microsoft has yet to
address. Some will suggest that it is a problem with add-ons but the
problem will occur under a clean install of Windows 9x/ME/2K/XP and a fresh
install of MS Office. If an MS Office application acts "hinky" then check
if it actually got unloaded by looking in Task Manager's Process tab.
Outlook stuck in memory can actually cause other problems with other
applications, too. Word (winword.exe) has the same problem of not always
fully unloading when exited. The rebooting works because that ends up
wiping out the remnant program that got stuck in its exit process. There is
a utility out there (I'd have to go searching again) that attempts to kill
off the remnant and hung outlook.exe and winword.exe processes. I remember
trying it for a couple days but it had artifacts in its behavior that I
didn't like (and don't recall now) so I got rid of it. So I'm still stuck
with occasionally checking for outlook.exe and winword.exe - on any machine,
even those that I haven't setup - when MS Office apps don't behave.
--
__________________________________________________
E-mail: Remove "NIX" and add "#LAH" to Subject.
__________________________________________________