Comments inline.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
An Chi said:
-----------------------------------------
SentOnBehalfOfName Approach:
-----------------------------------------
I've actually tried setting SentOnBehalfOfName in Item_Open() but the
replies were still going to the original sender.
This is probably due to either:
1. the SentOnBehalfOfName was set to an external email address? (less likely?)
Not recommended. SentOnBehalfOfName is designed to facilitate sending as another Exchange user.
2. the Outlook Add-In installed on my clients' Outlook that uses a
customised send() for all customised forms?
Impossible to say, not knowing what the add-in actually does.
If your primary goal is to control who replies are sent to, use the ReplyRecipients collection.
I was told the customised send() is required because all outlook customised
forms:
1. do not display on preview panel, and
True, only if the custom form contains code behind it. Again, we don't know what the add-in is doing, though.
2. do not print as displayed.
True, and an add-in is the best solution.
-----------------------------------------
What I'm trying to achieve:
-----------------------------------------
Just want to express my appreciation that you are actualy willing to discuss
what exactly I'm trying to achieve here.
Because you are right, I have a feeling I'm on the wrong track.
The process I'm after:
Person A sends a customised form (and specifies who Person C and D are) to
person B.
Person B approves/rejects the form and when click 'reply' sends it to person
C and D.
Person C and D receives the form (including the approval status) and forward
it to external parties
As the page I suggested earlier makes clear, this is going to be possible only if the form can be published to the Organizational Forms library or each user's Personal Forms library. Furthermore, sending a message that uses a custom form to external parties is generally a bad idea, because it may cause problems with attachments.
We are happy to make comprises as long as people can preview/print the form
as expected and the solution is easy to publish across the firm.
If custom script behind is not the norm, should I be reading up on
macros/add-in?
Macros are not a viable solution. An add-in could do it.
What you may have missed is that, in general, custom message forms with script behind them are not a good idea, unless you're using them strictly internally. See
http://www.outlookcode.com/article.aspx?id=61 for details on the issues involved.
Before you get too far down the custom form road, why don't you explain just what you're trying to accomplish? There may be a better solution.