'Save Sent Item' option in new msg

Topic

New Reply

Scenario: User with Outlook 2007 running on Microsoft Exchange Server (2003).

I have a user who, when creating a new message – always goes to OPTIONS – ‘SAVE SENT ITEM’ and chooses a sub folder to save a copy of the sent message prior to actually sending the message.

This worked fine until I made her move all her inbox subfolders to a PST (Personal Folder) file.

If she chooses “Save Sent Item” and then ‘Other Folder” and chooses one of the folders of her PST listing, Outlook throws the message “The folder you have selected is not a subfolder of the default store” and it will not allow her to choose a folder in the Personal Folder group – it has to be a folder on the live Xchange mailbox. We discourage users from keeping multiple subfolders on Exchange due to storage size issues, and we prefer they keep mail they want to archive in PST files.

Yes, she can go MOVE the message from her sent items to her PST after it is sent. But that is more steps this user just doesn’t want to do.

Do you know if this is by Microsoft design? Any work-arounds?

pribb

(I should add it throws the same message when I, or any of my co-workers, try this. So it is not just an error on her machine/mailbox)

Reply | Quote

Replies

More like a Microsoft omission. Few of us Outlook users can’t list ten things we hate about Outlook.

See if this code, installed on the users machine locally as a workaround, helps solve the problem: http://lounge.windowssecrets.com/index.php?showtopic=401049&view=findpost&p=402534 Note the instructions on installing it into the ThisOutlookSession Module, and also the code note two posts later.

(I have been less active in the Outlook forum because I switched jobs to a company using Notes. Notes is one ugly and cursed interface, with some incredibly dumb features such as dialogs you cannot back out of, but there are some things it does, such as what you are looking for, very nicely.)

Reply | Quote

Thanks John,

I tried this a bit, but had trouble with the “ThisOutlookSession” thing — but we have a VBA expert here, so I’m going to ask her help to build this module. What I have tried so far using that code does not work, but it is probably a problem with my attempts at creating that module. From what I am reading (about that code in that thread) – this won’t necessarily make the Save Sent Item feature work, but instead it will prompt for a save location when they choose send?

pribb

Reply | Quote

I tried this a bit, but had trouble with the “ThisOutlookSession” thing — but we have a VBA expert here, so I’m going to ask her help to build this module. What I have tried so far using that code does not work, but it is probably a problem with my attempts at creating that module. From what I am reading (about that code in that thread) – this won’t necessarily make the Save Sent Item feature work, but instead it will prompt for a save location when they choose send?

Last question first – yes, it’s a workaround that prompts for a target Folder to save the message on EVERY Message sent.

On using the code, you should be able to copy the text and simply place it in the “ThisOutlookSession” module. When you open the Outlook VBE (Alt-F11) on t he upper left side you should see something like the attachment (your user may not have Forms and Modules folders); click on Microsoft Office Outlook Objects to display the ThisOutlookSession module, double-click on the “ThisOutlookSession” to open it, it should be displayed in the code pane on the right side of the VBE window. Paste the code in there (unless there’s other stuff already there in which case we would want to see that there’s no conflicts).

Remember to close Outlook, say yes to the “save changes” question and restart Outlook. You may also need to change Outlook’s macro security settings – signing the project makes using the code more convenient and seamless.

Reply | Quote

Excellent! This works well! Thank you so much for the work-around solution to keep this user happy.

I was surprised we did not have the macro security settings set by group policy, so we were able (thankfully) to change those to make this work pretty seamlessly.

Now — is someone going to suggest to Microsoft that maybe they change/fix this going forward?

pribb

Reply | Quote