Read page vs Composed page

[Long Nguyen]

(Outlook 2002 SP2)

I have a custom form that uses both Compose and Read Page.

What I have found is that on Read Page the behaviour of fields are handled
differently by Outlook form system. For example I have a text field which is
bound to a user defined field (and so this field is available on both
pages), but when I used the Item_CustomPropertyChange subroutine to detect
when that field become active, it only works on the Compose Page not the
Read Page. That is after the form has been sent, users open the form (and so
they now see the Read Page), clicking on the field would not be detected by
Item_CustomPropertyChange subroutine.

Is that the way it is supposed to work?

Thanks
Long

 

[Sue Mosher [MVP-Outlook]]

If the form runs code when you use Run This Form in design mode, but doesn't
run code after you have sent or saved an item using the form, you probably
have done something to "one-off" the form. Outlook 2003, Outlook 2002,
Outlook 2000 SP2 and Outlook 2000 or 98 with the Email Security Update will
not run code on one-off forms; see http://www.outlookcode.com/d/secforms.htm
for more information on this issue.

To ensure that a form does not one-off:

-- Make sure the "Send form definition with item" box on the (Properties)
tab of the form is *not* checked. [1]

-- For in-house corporate use with Exchange Server, publish the form to the
Organization Forms library or a public folder's forms library, as
appropriate for your application.

-- For collaboration via the Internet, publish your form to your Personal
Forms library. Save it as an .oft file and send it to other people who need
to use it with instructions to publish it with the same form name that you
used.

Many other things can cause one-off forms. If the above steps don't work on
a new item created with your form, see
http://www.slipstick.com/dev/formpub.htm#oneoff for other possible causes.

[1] Whenever you publish a message form, Outlook will suggest that you may
want to check the "Send form definition with item" box to ensure that the
recipient will have the form, especially if you're sending to someone via
the Internet. In the current Outlook security environment, this suggestion
is obsolete. Ignore it unless your form has no code behind it.

 

[Long Nguyen]

Thanks Sue for the information. I did not save the form with item and I
store the form in a public folder so if the form became one-off it must be
some other reasons.

Another question: The form I create have the same layout and fields in both
Compose and Read page, but on the Read page the fields I mae the fields
read-only. I
provide an Edit button on the Read page (which is visible to only certain
users) and if this button is clicked then I unlock the fileds (to allow
users to edit the fields). What I have found is that with date fields when I
unlocked them they no longer be able to recognise word values such as
"today", "next week" etc. Is this the way it is supposed to behave?

Thanks
Long

If the form runs code when you use Run This Form in design mode, but doesn't
run code after you have sent or saved an item using the form, you probably
have done something to "one-off" the form. Outlook 2003, Outlook 2002,
Outlook 2000 SP2 and Outlook 2000 or 98 with the Email Security Update will
not run code on one-off forms; see http://www.outlookcode.com/d/secforms.htm
for more information on this issue.

To ensure that a form does not one-off:

-- Make sure the "Send form definition with item" box on the (Properties)
tab of the form is *not* checked. [1]

-- For in-house corporate use with Exchange Server, publish the form to the
Organization Forms library or a public folder's forms library, as
appropriate for your application.

-- For collaboration via the Internet, publish your form to your Personal
Forms library. Save it as an .oft file and send it to other people who need
to use it with instructions to publish it with the same form name that you
used.

Many other things can cause one-off forms. If the above steps don't work on
a new item created with your form, see
http://www.slipstick.com/dev/formpub.htm#oneoff for other possible causes.

[1] Whenever you publish a message form, Outlook will suggest that you may
want to check the "Send form definition with item" box to ensure that the
recipient will have the form, especially if you're sending to someone via
the Internet. In the current Outlook security environment, this suggestion
is obsolete. Ignore it unless your form has no code behind it.


--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

(Outlook 2002 SP2)

I have a custom form that uses both Compose and Read Page.

What I have found is that on Read Page the behaviour of fields are handled
differently by Outlook form system. For example I have a text field which
is
bound to a user defined field (and so this field is available on both
pages), but when I used the Item_CustomPropertyChange subroutine to detect
when that field become active, it only works on the Compose Page not the
Read Page. That is after the form has been sent, users open the form (and
so
they now see the Read Page), clicking on the field would not be detected
by
Item_CustomPropertyChange subroutine.

Is that the way it is supposed to work?

Thanks
Long

 

[Sue Mosher [MVP-Outlook]]

There are plenty of other possible causes for one-offing. You can confirm
whether that is indeed what's happening by checking the value of the
MessageClass property for problem items.

The behavior you're seeing with date fields is not a known issue.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers