First, a terminology clarification: What are sent are items or messages, not
forms. The form is only the UI/code template.
Since the user if creating a new item by replying, you can put code in the
Reply event handler to close the parent item, e.g.:
Function Item_Reply()
Const olDiscard = 1
Item.Close olDiscard
End Function
Sue Mosher
"Randy" wrote:
> Hi Sue, and txs for your reply.
> The form is a very simple one, and has just two fields: COMMENTS and
> HISTORY (both multiline text fields).
> Here´s an example of the way the form will work:
> User A opens the form (Tools/Form/Choose Form), types in a few
> comments in the COMMENTS texbox, then sends the form to user B.
> Before the form is sent:
> 1.- the current date and time are added to the user´s comments
> 2.- the contents of the COMMENTS field are added to the HISTORY field
> 3.- the COMMENTS field is cleared.
> User B opens the form from his/her Inbox, clicks on Reply, types his/
> her comments in the COMMENTS field and sends the form to user C.
> Before the form is sent, date and time are added to user´s
> comments.... and so on.
> The forms that arrive in the users´ Inboxes are what I call "parent"
> forms. Users open the parent forms and then click on Reply, launching
> what I call a "child" form - the one they will use to type in their
> comments.
> Obviously, when the child form is launched, the parent form remains in
> the background. Once an user sends out the child form, he will still
> have to close the parent one.
> Hope that this information will clarify what I am trying to do. Txs a
> lot again for your reply!
> Best,
> R.
> .
>