I understand that there is not supposed to be files there but the fact
remains that
there is files there that the users do not want there.
I need to send out a memo on how to clean that folder
<Vanguard>
|>|>> The OLKEA is the folder used by outlook when you launch email
|>> attachments.
|>> It is not cleaned by the delete temporary Internet files button in IE
|>> So how can a regular joe user clear this folder?
|>> Its not browseable with windows explorer
|>>
|>
|>See
http://support.microsoft.com/?id=817878.
|>
|>When you
view an e-mail that has inline attachments, like embedded
|>images (not linked ones), a copy of the inline attachment is created in
|>the OLKnnnn folder. When you select a different e-mail or exit Outlook,
|>those files are deleted.
|>
|>When you open an attached file (i.e., not inline) but don't save it, the
|>OLKnnnn path is used to save a temporary copy of that file. When you
|>close the application used to display that attached file, it is unlikely
|>that that the application will delete the temporary copy of it. That
|>temp file won't get deleted until you exit Outlook.
|>
|>Since the name of this temp path changes (OLKnnnn, where nnnn is some
|>random string), perhaps you are looking in an old path that didn't get
|>purged because Outlook crashed instead of exiting properly. That means
|>any subsequent use of that same path won't have Outlook remembering that
|>it opened it to then close it because that instance of Outlook didn't
|>open it. It may also be a different OLKnnnn path that the current
|>instance of Outlook is using. For example, mine is currently called
|>OLK1965.
|>
|>Also note the behavior mentioned at
|>http://www.outlook-tips.net/archives/20030828.htm regarding changing to
|>view a different mail item while you still have an attachment open from
|>the prior mail item. This is because, as noted above, the application
|>you use to view the attached file is not Outlook and so it doesn't
|>perform the temp file synchronization of Outlook (but Outlook may delete
|>the file when it is exited which results in the application erroring
|>should you attempt to edit it but the application may lock the file
|>which means Outlook cannot delete it on its exit). For me and for the
|>few tests that I made, I cannot get .jpg files to remain in the OLK*
|>folder when Outlook exits. The viewer still shows the .jpg file but its
|>source file is gone (i.e., the viewer is showing the copy that is in
|>memory). When I open a .doc attachment in an e-mail and exit Outlook,
|>the file remains in the OLK* folder because Word still has a file handle
|>to it (the file is open in write mode and not just read mode). Exiting
|>Word does not then delete the temp file (i.e., it gets left behind).
|>
|>You are asking non-integrated applications, Outlook and some viewer app,
|>to perform coordinated functions but they won't. There are far too many
|>apps that could be used as viewers for Outlook to bother monitoring
|>which opened an attachment, and there are far too many e-mail programs
|>for viewer/edit apps to monitor which e-mail client created the file
|>that the viewer/edit app opened. Running the Disk Cleanup wizard won't
|>help since it doesn't purge the OLK* folder. CCleaner lists Office XP
|>for an application that it cleans out files
|>(http://www.ccleaner.com/features.asp) but doesn't specifically mention
|>the OLK* folder. You could ask in their forum if the OLK* folder is
|>included. I haven't used this utility so I cannot vouch for this
|>stability, robustness (so that it doesn't cause damage), that it has no
|>covert payload (like spyware), etc., but I have seen it get good ratings
|>as known review sites and many users have found it helpful. You could
|>just put a shortcut to "Documents and Settings\<youraccount>\Local
|>Settings\Temporary Internet Files\OLKnnnn" (or wherever is you OLK
|>folder) in your Office startup folder to make it easy to periodically
|>open that folder and check for crap that got left behind. I suppose you
|>could also write a .bat file that deletes all files in that folder and
|>then schedule a run of it in Task Scheduler.