Outlook Form (2002, SP3 + post hot fix) Script Not working in some contact folders

[Neo]

My custom form has been working fine for a year. Today I published a
new version (very few and insignificant changes) and suddenly none of
the scripts work (but only in some Exchange contact folders, not all!).


Is this a cache issue? I have cleared cache in the Manage Forms area. I
have deleted the original form from the Org Forms library and
re-published it. I have also saved the form under a different name and
published it under a different name. I have republished the original
form again all of which has resulted in no difference. In several
folders (I have a view of multiple mailboxes in my profile).

When in a contact folder of a user not working correctly, I can run the
form (from design view), and it works just fine. Strangely, other users
that have access to the same "not working" Exchange contact folders see
that the form is working fine.

In each instance, some folders show
Environment: Outlook 2002, Office SP3 version 10.6515.6735

Any thoughts, greatly appreciated.

Jason Davey
(e-mail address removed)

 

[Sue Mosher [MVP-Outlook]]

There are two major causes of code in an Outlook form not running -- 1) security settings in Outlook 2003 and 2) the broader form script security features introduced with the Outlook Email Security Update.

#1: Outlook 2003 includes a new setting -- turned off by default -- to allow forms in shared mailboxes to run script. You can change the setting by choosing Tools | Options | Other | Advanced Options and checking the box for Allow script in shared folders. See http://www.outlookcode.com/d/ol2003problems.htm#mailboxscript for more information on this setting and a comparable one (on by default for public folders).

#2: 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 published 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.outlookcode.com/d/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

 

[Jason Davey]

Sue: Thanks for your response. In the past 30 minutes, this is what I've
learned.

I was logging into a server using a global domain account name "user1"
but user1 Outlook profile was configured to pull data from "user2". I
changed the account settings so that user1 was pulling Exchange data
from user1 and that enabled the form scripting.

However, now I can't run forms from other contact folders in my profile
"user3" for example so I suspect from what you said, I don't have
permissions to run scripts on a form from other's folders???

The published form is not a one off - as it is published in the
Organizational Forms library. I also made sure the "send form
definition" property was unchecked (it was unchecked as I suspected).

How then, can I check to see if my local contact folder (user1) has the
permissions to run scripts on shared folders (user2) using Outlook 2002
which doesn't benefit from the User Interface control available in
OL2003??

Thanks,

Jason

 

[Jason Davey]

I found a fix where in OL2002, you change a registry setting to allow
sharing of scripts across contact folders.

for more information, go here:

http://www.outlookcode.com/d/secforms.htm#trust


Jason Davey
Senior Engineer
Versys Corporation
San Francisco, CA, USA
(e-mail address removed)

 

[Sue Mosher [MVP-Outlook]]

How then, can I check to see if my local contact folder (user1) has the

permissions to run scripts on shared folders (user2) using Outlook 2002
which doesn't benefit from the User Interface control available in
OL2003??

There's nothing to check. You will not be able to run form scripts for items in another user's folder until you set the necessary registry value, as described at http://www.outlookcode.com/d/ol2003problems.htm#mailboxscript (change 11.0 to 10.0 for OL2002)

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