Read reply only active when replying from particular address?

[Guest]

I'm creating a vacation and trade request form based on the message form.

The trade request portion has a drop down box for Name1 and a dropdown box
for Name2.

I want the 1st employee to send the form to the employee they are trading
with, get approval of some sort in the body then have that 2nd employee send
the form on to the vacation approver (supervisor).

My problem is that twofold. One when the mail is sent to the 2nd person for
approval they see my "Read page" options that I use to approve or deny the
request which isn't ideal. Not a real deal breaker but just not desiraable
either.
Question 1: Is there a way to get the read page to only display when viewed
by the email address used by the vacation approval supervisor?

Second issue is that after I send the email back to the employee's with the
approval or denial of their request (which is done from read reply
prompts/values) the person who recieves the email can change those value
boxes to their hearts content.

Question #2 Is there a way to "freeze" the options I have entered in the
read reply after I send it back to an employee?

Thanks for any help.

 

[Sue Mosher [MVP-Outlook]]

Question 1: Is there a way to get the read page to only display when viewed

by the email address used by the vacation approval supervisor?

Wrong question. The right question would be, "Is there a way to get certain controls on the read page to display only when viewed ..."? The key concept here is state management. If you track what "state" the item is in (original, on its way to 2nd person, at final approver, etc.), you can use code in the Item_Open event handler to show/hide the controls you want to be visible for that state.

Question #2 Is there a way to "freeze" the options I have entered in the
read reply after I send it back to an employee?

The same technique would apply.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

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