Is Reply All or Forward the Way to Go?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi-
I'm need to come up with an Outlook form that: 1.) keeps past recipients of
the e-mail on all future e-mails; and, 2.) doesn't drop any past attachments
to any future e-mails.

I've attempted creating my own items to collect names listed in the to: and
from: items in the compose page and trying to load them into to: line on the
read page, but haven't been successful yet.

We'll use the form when my agency has to assign kids for behavior or
emotional problems to institutions, a lot of people have to see the same
information to make the right decision as quickly as possible.

Any help is really appreciated.
 
It sounds like you want some sort of routing form. Look for "routing" in the
search at www.outlookcode.com for some examples that at least should give
you a starting point.
 
Mr. Slovak-

First, I've got to apologize, I'm still learning how to use forums and
mistakenly posted the same message here and in Forms. I thought I had
already deleted one.

Anyway, routing (very cool application, hope to use it someday) would work
if I knew in advance who would get the message. But I don't. And the
message has to hit everybody (including past recipients) with each new
sending.

I think I'm still stuck on looking for way of including (in a customized
message) either a 'forward to all' or a 'reply to all with attachments'
action. The other option I might have is figuring out a way to recalculate a
mail item (eg. bcc, to, etc.) at some point after a form has been opened.

With this approach I could stuff current mail items into user defined text
boxes upon form opening and then load the recipients back into the mail items
at the delayed or repeated calculation.

Thanks much for your earlier reply, I really appreciate it.
 
Any built-in reply or reply all method does not include attachments. And
there is no forward to all method, that would have to be simulated.

Frankly, any use of the Outlook object model to do what you want runs a real
risk of changing at least some of the properties of the original in the
copy. Using an Extended MAPI wrapper such as Redemption might be better
since you can write some Outlook read-only properties before you save the
copy the first time. After that those properties would be read-only just as
in Outlook code.

You might just have to live with at least a few of the original properties
being changed in the copy.
 
Very tantilizing. Do you know where I should start looking for code for a
simulated forward to all method?

Trying to simulate a 'forward to all' method by recalculating mail item
values after a form has been opened is not worth the effort ?

I really appreciate your advice-
 
I don't have any links I can provide for that. It would be all detective
work on your part. I've never been tasked with those requirements for any of
my projects, so I have no immediate answer.

I do sometimes make copies of items using Redemption using the RDO objects
and then I can alter some normally read-only properties before I initially
save the new RDO item. You can browse around the Redemption Web site for
code samples that might help (www.dimastr.com/redemption and
www.dimastr.com/redemption/rdo).
 
Mr. Slovak-

I'm pretty embarassed. I realized last night that if I just put a user
defined item on the 'read' page of the form and set it's default value to (To
+ ': ' + From + ': ' + CC) and set the CC default value on the 'compose' page
then each time I forwarded the e-mail all past recipients of the e-mail would
get each new copy of it.

It's a little cludgy, e-mails get duplicated in the cc: line, but it works.
I can figure out something more elegant later.

I'll now post my next drop dead challenge on this project and hope you'll
see it and respond....:)

Thanks again.
 
Back
Top