OL2K - 2003 Issues

[Jim Fanning]

I am new to working with Oulook Forms. I have an .oft created in OL2003 that
we would like to "give" to our customer so they can place orders. They have
OL2003 w/Exchange Server. They will be sending the form to us, we have OL2K
and are using a POP3 MDeamon.

We've tried testing the form but, have hit a "snag". We receive the form in
OL2K fine, but when we "forward" a response back to our customer, they only
see the message field. Is there a "fix" for this?

Thank you,
Jim Fanning

 

[Sue Mosher [MVP-Outlook]]

No, there is no practical fix for this. I'd recommend using some other data gathering method other than an Outlook form template.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Hollis Paul [MVP - Outlook]]

We've tried testing the form but, have hit a "snag". We receive the form in
OL2K fine, but when we "forward" a response back to our customer, they only
see the message field. Is there a "fix" for this?

Probably not. Forms do not survive well outside of an Microsoft/Exchange
environment. But, if it is ever to work, you must be sending your reply back
to them using the TNEF wrapper, something you have never heard about. However,
to control this you need to open the contact data item for this customer,
right-click the email address you are using, choose properties, and on the
bottom of the properties panel is a check-box that is labeled "Always send to
this recipient using rtf", That box must be checked and the properties ok'd
and the contact item saved.

You have also published the form to your personal forms library, have you not?
And they should not be sending the form design with the message.

 

[Parham]

Dear jim :

try to uninstall the following patch and see if the problem solved or not :
"kb 913807"

 

[Sue Mosher [MVP-Outlook]]

That update has nothing to do with the problem, AFAIK. The article at http://support.microsoft.com/?id=907985 explains the issue, which is related to SP2.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers