Article ID: 207430
Article Last Modified on 11/23/2006
APPLIES TO
- Microsoft Outlook 2000 Standard Edition
This article was previously published under Q207430
SUMMARY
This article explains the differences between fields within an Outlook item and controls on an Outlook form. In addition, this article also provides an overview of how to use Visual Basic Scripting Edition (VBScript) to reference fields and controls.
NOTE: Programming concepts and syntaxes in this article also apply to programming with Visual Basic for Applications. The only difference is in how you reference the item.
MORE INFORMATION
The Difference Between Fields and Controls
Fields (also referred to as properties) actually store data within an Outlook item, such as a contact or a task. The Subject field of a mail message is an example of a field within an item. Fields can be either a pre-defined field that Outlook makes available (such as Subject), or a user-defined field that you can create for your own purposes.
Controls are objects, such as a text box, a scroll bar, a list box, or a command button, that let users control, enter, or change data. When designing a custom Outlook form, you place controls on a form to display data or choices, perform an action, or make the form easier to read.
Controls by themselves, provide no storage for the data that is associated with them. In the majority of cases, controls are used to display the contents of a field within the item and therefore should be linked, or bound to a particular field.
Using Fields and Controls
All of the pre-defined form controls (To, From, Cc, and such) are automatically bound to corresponding standard Outlook fields. However, if you create a custom form and add a custom control, you should make sure that a field is designated to store the data that is associated with the control.
For example, suppose you want to add a text box to your mail message form that enables people to enter their office location. When you design the new form, there are a few ways to accomplish this.
The easiest way is to click the New button on the Field Chooser to create the Office Location field. Then you can simply drag the field from the Field Chooser onto the form. Outlook automatically creates a text box on the form and bind it to the Office Location field.
You can also add a text box control by dragging the control from the Control Toolbox. This creates the text box on the form to provide a place to enter the office location. Since the control itself provides no storage for the item, the text you typed into the office location is lost when you send the item to someone. You must also bind the control to a field to provide storage for the data. This way, when someone fills in the field and sends the item, the data is preserved when the item is received by someone else.
To Place a Control on a Form
- Create a new item, such as a new message.
- On the Tools menu, point to Forms and then click Design This Form, to switch to form design mode.
- On the Form menu, click Control Toolbox.
- Drag the control type that you want from the Control Toolbox to the place on the form where you want the control to appear.
To Create a Field to Provide Storage for the Control
- If the Field Chooser window is not open, on the form Form menu, click Field Chooser. You can also open the Field Chooser from the main Outlook View menu if you are not in design view and have no items open.
- Click New to open the New Field dialog box.
- In the Name box, type a name for your new field. In the Type list, click to select the data type. In the Format list, click to select the format for the field.
- Click OK.
To Bind a Control to a Field
- Starting in form design mode, use the right mouse button to click the control, and then click Properties on the shortcut menu.
- In Properties, click the Value tab.
- Click Choose Field to select the field you want to bind to this control. You can also click New to create a new field instead of using the Field Chooser.
Using VBScript to Change Field and Control Values
Microsoft 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 professionals 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 a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:
For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:
The Outlook object model syntax for referencing controls is quite different from the syntax for referencing fields. The following examples use VBScript to illustrate syntax, but the same code examples can be used with Outlook Visual Basic for Applications, or Automation if you make appropriate modifications for referencing the Item or Inspector objects.
Syntax for Accessing a Control on a Form
Generic: Item.GetInspector.ModifiedFormPages("PageName") _
.Controls("ControlName").Property = <value>
Example: Item.GetInspector.ModifiedFormPages("Message") _
.Controls("OfficeLoc").Visible = True
Syntax for Accessing a Standard Outlook Field
Generic: Item.FieldName = <Value>
Example: Item.Subject = "This is a new subject"
Syntax for Accessing a User-defined Field
Generic: Item.UserProperties.Find("FieldName") = Value
Example: Item.UserProperties.Find("OfficeLoc") = "Blg 4, 1234"
Usage Examples
In the "OfficeLoc" example above, these two example lines of code have the same effect on the form.
Item.UserProperties.Find("OfficeLoc") = "Blg 4, 1234"
-or-
Item.GetInspector.ModifiedFormPages("Message").Controls _
("OfficeLoc").Text = "Blg 4, 1234"
The first example changes the Office Location field to a new value and the second line changes the text box control Text property to the new value. Since the control is bound to the field, a change made in either place affects the other.
Tips for When to Use Each Method
When you want to change a "property" (color, visibility, bold, italic) of a control, you must use the control syntax. You cannot set control properties by changing the field.
Example: Make the Office Location textbox not visible Correct: Item.GetInspector.ModifiedFormPages("Message") _ .Controls("OfficeLoc").Visble = False Incorrect: Item.UserProperties.Find("OfficeLoc").Visible = FalseWhen you want to change the value of the data (text, number, date) use the field syntax.
Example: Change the office location to "Building 5" Preferred: Item.UserProperties.Find("OfficeLoc") = "Building 5" Also works: Item.GetInspector.ModifiedFormPages("Message") _ .Controls("OfficeLoc").Text = "Buiding 5" Example: Change the subject to "This is a subject" Preferred: Item.Subject = "This is a subject" Also works: Item.GetInspector.ModifiedFormPages("Message") _ .Controls("Subject").Text = "This is a subject"- Programmatically using the Controls collection requires that the form is open. When the form is closed, the control is not available. However, fields are always available and you can use references to the field in your code at all times. For example, suppose you want to be able to start from one item and click a button that changes the subject for a different item. If you use fields, you do not have to write code to open the form. If you access the control, your code must include lines to display the form. Displaying the item takes more code and more time. Fields work whether the form is loaded or not, regardless of what page the control is on, and affect all the controls that display that field, not just one. Using fields also insures that other fields calculated from the original update.
REFERENCES
For additional information about available resources and answers to commonly asked questions about Microsoft Outlook 2000 solutions, please see the following article in the Microsoft Knowledge Base:
146636 OL2000: Questions About Custom Forms and Outlook Solutions
Additional query words: OutSol OutSol2000 automation programming OL2K
Keywords: kbhowto kbprogramming KB207430
