OL97: Supported Outlook Forms Control EventsLast reviewed: March 2, 1998Article ID: Q171246 |
The information in this article applies to:
SUMMARYThis article describes the three events that are supported by a form's fields and controls in Microsoft Outlook 97.
MORE INFORMATIONMicrosoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:
http://www.microsoft.com/support/supportnet/refguide/default.aspControls in forms in Outlook can perform three types of events:
Click PropertyChange CustomPropertyChange The Click EventThe Click event occurs when the user clicks a form control. You can create as many Click event procedures as you have controls on a form. The name of each event procedure is the name of the control (such as "CommandButton1"), followed by an underscore character (_) and the word "Click." The following example displays a greeting containing the log on name of the current user whenever the button named "CommandButton1" is clicked:
Sub CommandButton1_Click() MsgBox "Hello " & Application.GetNameSpace("MAPI").CurrentUser End Sub NOTE: The Message and Note form controls do not support the Click event. NOTE: If a control is bound to a field, then the Click event will not fire. Instead of using the Click event, you should typically use the CustomPropertyChange or PropertyChange event when a control is bound to a field. For more information about the Click event and bound controls, please see the following article in the Microsoft Knowledge Base: Article-ID: Q166853 Title : OL97: Bound Control Does Not Support Click Event The PropertyChange EventThe PropertyChange event occurs when one of the item's standard properties is changed. The property name is passed to the procedure, making it possible for the procedure to determine which property was changed. The following example disables setting a reminder for an item:
Sub Item_PropertyChange(ByVal myPropertyName) Select Case myPropertyName Case "ReminderSet" MsgBox "You cannot set a reminder on this item." Item.ReminderSet = False Case Else End Select End Sub The CustomPropertyChange EventThe CustomPropertyChange event occurs when one of the item's custom properties is changed. These properties are the user-defined fields added to the item at design time. The property name is passed to the procedure, making it possible for the procedure to determine which field was changed. The following example enables a control when a Boolean field is set to True.
Sub Item_CustomPropertyChange(ByVal myPropName) Select Case myPropName Case "RespondBy" Set myPropChg = myItem.GetInspector.ModifiedFormPages Set myCtrl = myPropChg("Page 2").Controls("DateToRespond") If myItem.UserProperties("RespondBy").Value Then myCtrl.Enabled = True myCtrl.Backcolor = 1 Else myCtrl.Enabled = False myCtrl.Backcolor = 0 End If Case Else End Select End Sub Adding a Control and an Event to a Custom FormTo add a control and an event to a custom form, follow these steps:
REFERENCESFor more information about creating solutions with Microsoft Outlook 97, please see the following articles in the Microsoft Knowledge Base:
Article-ID: Q166368 Title : OL97: How to Get Help Programming with Outlook Article-ID: Q170783 Title : OL97: Q&A: Questions about Customizing or Programming Outlook |
Additional query words: OutSol OutSol97
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |