A problem occurs with custom forms that use the UserProperties.Find method and formulas in Outlook 2002 Service Pack 3 (839410)
The information in this article applies to:
- Microsoft Outlook 2002 Service Pack 3 (SP3)
SYMPTOMSAfter you apply Microsoft Outlook 2002 Service Pack 3 (SP3), Outlook custom forms may not function correctly. The custom forms may exhibit a variety of problems that did not occur before you installed the service pack. When you use the UserProperties.Find method with a custom field that contains a formula, the custom field value may change. You may also receive the following error message: The Operation Failed CAUSEWhen you use the UserProperties.Find method with a custom field that contains a formula, this may cause the custom field value to change. How the custom field value changes depends on the formula that is in the custom field.
You may receive the error message that is mentioned in the "Symptoms" section if the formula does not produce valid data for an Outlook field. For example, if you have a formula that sets a text field to a value of NULL, and you reference that field by using the UserProperties.Find method, you may receive the error message that is mentioned in the "Symptoms" section. Because NULL is not a valid value for an Outlook text field, an empty string ("") value must be used to set an Outlook text field to a blank value.WORKAROUNDTo work around this problem change the Microsoft VBScript code in the form so that the VBScript code uses the following syntax instead of using the UserProperties.Find method syntax: UserProperties('fieldname') To make this change, you can use the Replace command of the VBScript Editor. To do this, follow these steps: - Open the form in Design mode.
- On the Form menu in the VBScript Editor, click View Code.
- On the Edit menu, click Replace.
- In the Find what box, type UserProperties.Find(.
- In the Replace with box, type UserProperties(.
- Click Replace All.
- Close the VBScript Editor.
- Republish the form.
RESOLUTIONA hotfix for this issue is currently in the development process. More information will be provided when the hotfix becomes available.
Modification Type: | Major | Last Reviewed: | 3/8/2005 |
---|
Keywords: | kbprb KB839410 kbAudDeveloper |
---|
|