The properties of the message <message> have been changed

[Jim S.]

I'm implementing a custom form solution for phone messages. Custom form is
published to the Organizational Forms library. Everything works perfectly,
except that when a message is opened, on closing the message the user gets a
message "The properties of the message <message> have been changed. Do you
want to save changes to this message?"

Any ideas?

 

[Sue Mosher [MVP-Outlook]]

That warning message means just what it says: Some property of the item has
changed since the item was opened. To help you troubleshoot and track down
which property that might be, you can put code in the form's PropertyChange
and CustomPropertyChange events.

 

[Jim S.]

Thanks, Sue. I've been able to track the issue to the Subject property. The
value of the Subject property is set to calculate automatically based on the
user defined fields Caller and Phone (i.e. [Caller]&" "&[Phone]).

Will the PropertyChange event fire everytime the recipient opens the message
or is there a way to trap or prevent the event from firing for the recipient?

 

[Sue Mosher [MVP-Outlook]]

You cannot prevent an event from firing. One solution would be to save the
item immediately after it opens. Another would be to use code, not a formula
to set the value of the Subject property and only do it when the constituent
properties change.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

Thanks, Sue. I've been able to track the issue to the Subject property. The
value of the Subject property is set to calculate automatically based on the
user defined fields Caller and Phone (i.e. [Caller]&" "&[Phone]).

Will the PropertyChange event fire everytime the recipient opens the message
or is there a way to trap or prevent the event from firing for the recipient?

That warning message means just what it says: Some property of the item has
changed since the item was opened. To help you troubleshoot and track down
which property that might be, you can put code in the form's PropertyChange
and CustomPropertyChange events.