View Single Post
  #5  
Old May 5th 06, 02:31 PM posted to microsoft.public.outlook.program_forms
[email protected]
external usenet poster
 
Posts: 7
Default custom form as forwarded item not visible in other Exchange org


Sue Mosher [MVP-Outlook] wrote:
But did you actually change the Forward action to point to the published custom form? Forms can't be renamed, so I have no idea what you've actually done.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

wrote in message oups.com...

Sue Mosher [MVP-Outlook] wrote:
Make sure that the Forward action on the form is set to use your published custom form. Otherwise, the forwarded item will one-off.

wrote in message ups.com...
Hello,

I've created a custom form based on a message which allows to enter
data for a hardware purchase and a button to "Send to manager". The
user can fill this in and choose someone from the GAL to send the form
to.
The recipient receives this form (as a "note" icon in his inbox ?) and
when opening it he can approve the purchase and click on the approve
button or he can reject the purchase with a reject button. The form
thus has a different "read" and "compose page".
The problem is that whenever the user clicks approve the mail is
"forwarded" with a few lines of code to an external smtp-adres so the
form leaves the Exchange org. The recipient is also on Exchange, has a
copy of the form published in his Personal Forms Library and has the
flag "use MAPI Rich Text" in his Exchange properties in AD (on the
sending Exchange server).
However the recipient is receiving empty mails.
I had to go for forward because the approving manager upon opening the
mail the mail is "read" and cannot be resend from code without
forwarding it (I guess).
The code used behind the button is :

Sub CommandButton2_Click()
Set objNewItem = Item.Forward 'This is the line that causes the
error!
objNewItem.To = "
objNewItem.Recipients.ResolveAll
objNewItem.Send
End Sub

I really would appreciate some help on this.



Strangely enough it does mention in the forward action to use the
custom form...While testing I renamed the form to a something version 2
which didn't reflect in the action, it generated a runtime... Still the
mails turn up empty.
I then tought of the fact that one of the Exchange server might strip
off the TNEF but I don't think so. I simulated in a lab (2 exchange
servers , different org, just smtp connector) and the result is the
same. It keeps me puzzled.
If i send the initial form to the same recipient the mail gets through
in RTF and he can read the form. The forwarded one still turns up
empty.

Much obliged,
Steven


Hello Sue,

I checked like you said the forward action and found out that the name
is the correct name. I reselected it from my Personal Forms Library and
re-published it to make sure. Problem persists.
I have noticed however that when I just send a new e-mail to the
recipient specified in the code this recipient
(who is defined in my contacts and has the flag Send using Rich Text)
has the Let Outlook decide the best sending format showing up in the
properties. Is that normal.
Now if I fire up the form and put 2 recipients (an approving manager
and the
) in the to - field and select
's properties and change this to Send using Rich
Text and then send the form then
receives the
form as should. So I have the impression it is something to do with
Outlook...

best regards,
Steven

Ads