Forcing "From" field value in oft template document

[elle0612]

Hi

I am currently creating a simple template for use by some folks who will be
using the same Email account, and therefore already have priviledges to use
this account.

Because we will be constantly using this outlook form, I want to create one
template, with most of the fields we need already filled in - then we would
only need to call this standard outlook form from a button created on the
toolbar.

Typically, the oft template document won't save with the "From" field
already completed because when I call it back up as an Email form, it is
always blank again, so, how do I ready-populate this field programmatically
with a value using VBA in an oft template document.

Thanks

 

[elle0612]

I have just posted to an old answered post entitled - Opening a Template just
below this one, because, what I am trying to do involves that post - and I
need clarification about using templates via a button on the toolbar.
Thanks

 

[Ken Slovak - [MVP - Outlook]]

No unsent message will have From filled in. If this is the default email
account for those people you don't have to do anything. The From field will
fill in automatically with the sending email address. Otherwise you'd need
to use the SentOnBehalfOf property in your custom form. If this is with
Exchange then the users would need SendAs rights on that mailbox and the
default mailbox would be the one that you desire as the From address.

 

[elle0612]

I have noticed that when customizing a form (thanks for explaining about it),
you can add a "From" field which can be pre-filled (eg ABC London) when you
publish the form. I presume this should now work when the people using the
form have account rights to use that ABC London account, as well as their own
accounts.

What is the best way of distributing this form to all staff who will be
using it?


Thanks

 

[Ken Slovak - [MVP - Outlook]]

Deployment of the form depends on your organization. If you use Exchange and
have an Organizational Forms Library then that's the place to publish the
form. That makes it available to all users with no extra steps.

Otherwise the place would be each user's Personal Forms Library. In that
case an OFT is saved to the file system and each user must manually publish
the form. An alternative is a script that does the publishing for them,
which is more foolproof.