Automatic clearing of the Outlook attachments cache in with Outlook 2003.

[ubercaff]

Hello,

Is there any possible way to have Outlook automatically clear its
attachments cache when opening or closing the application? Read below
for my specific issue which is the foundation for my question.

I have a client who receives hundreds of E-mails with every day.
Most of these E-mails contain automatically generated TIF file
attachments which are specific documents that require data entry. All
of these attachments are named identically (image.tif.) The user
directly open's the attachment up from the message without saving the
file first. This situation creates a problem after the user reaches
over 100 files named in sequence. An example would be image (1).tif -
image (99).tif. Once the user hits that magical "(99)" mark, Outlook
refuses to open up anymore images of the same name. The only way that
I am able to restore the ability for my user to resume normal business
operations is to clear out the Attachments cache by hand. Since this
might happen 2-3 times a week, I am looking for an automatic way. Has
anybody heard of this issue and what did they do to resole it?

 

[neo [mvp outlook]]

What I would do is redirect Outlook's temp folder to unique location under
the %TEMP% folder. Once that is done, use a simple batch job (scheduled
task?) that clears the folder.

The reg key that controls the Outlook Secure Temp Folder folder is at:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security

 

[ubercaff]

What I would do is redirect Outlook's temp folder to unique location under
the %TEMP% folder. Once that is done, use a simple batch job (scheduled
task?) that clears the folder.

The reg key that controls the Outlook Secure Temp Folder folder is at:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security








- Show quoted text -

I already changed the temp directory to C:\outlooktemp to make it
easier for clearing it out manually. We created a scheduled task for
her computer that clears out the directory on a nightly basis, but I
am still wondering if there is any way to allow the application to
create temp files past *(99)*. Maybe like a registry change or
something like that. It just seems wrong that Microsoft would have a
bug like this. Unless of course, it is a "feature."