Template and VBScript

[rblowe]

Based on my current knowledge of Outlook templates, I believe the
following to be true:

When templates include VBScript code, that code does not get executed.

For example, I have a form that once a user hits Send, I write
information into the message body. If I publish this as a form, the
code does execute and I get the expected results. However, if I save
this a template (.oft), the code does not appear to get executed.

Correct?

Any thoughts on how to achieve the functionality (writing data into
message body upon submission) described above in a template (.oft
file)?

Thanks

 

[Sue Mosher [MVP-Outlook]]

Yes, that's true. Only published forms run code (except in extremely rare circumstances where the Exchange administrator allows .oft files to run code). You will need to continue using a published form.

 

[rblowe]

Thanks Sue, any thoughts on how I can send someone running Outlook a
form that they need to fill out and reply with to an address that is
not running Outlook? The key here is getting the form information
that was filled in by the user at the non-Outlook reply address. From
my post above I was going to try the route of sending a template with
some code that makes the form contents visible in the message body, but
that does not appear to be an option.

 

[Sue Mosher [MVP-Outlook]]

I would probably send them a Word document, protected for form fields, or build a web page and direct them there.

 

[rblowe]

Thank you for your prompt responses Sue, I really appreciate it.
Another question if you don't mind.

Can published forms be accessed via URLs or similar manner?

For example, say I know which form I want a user to reply to my email
with. Can I send a message with a link so that when the user clicks
it, the appropriate Outlook form is launched? Is this possible? And
better yet, if it is, can I pass parameters (to populate a form field
with a value) in the URL?

 

[Sue Mosher [MVP-Outlook]]

It can be done, but only for recipients internal to an Exchange organization because the technique uses a public folder to hold the a launcher form. See http://www.outlookcode.com/d/forms/formlauncher.htm