The information in this article applies to:
SUMMARYThis article provides an overview of programming Microsoft Outlook 98 using Automation from another program. 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 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 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/overview/overview.aspAutomation (formerly OLE Automation) allows one program to control another program by either issuing commands or retrieving information programmatically. You can use the code examples in this article in Microsoft Word 97, Microsoft Excel 97, Microsoft Visual Basic, or any other program that supports Automation. Early vs. Late BindingYou can use either "early" or "late" binding to start an Automation session. Late binding uses either the GetObject or CreateObject function to initialize Outlook. For example, the following code sets an object to the Outlook program, which is the highest level object in the Outlook object model. All Automation code must first define an Outlook.Application object in order to access any of the other Outlook objects below that.
To use early binding, you first need to reference the available Outlook
object library. To do this from Visual Basic (VB) or Visual Basic for
Applications, follow these steps:
Once you reference the Outlook object library, you can use the following syntax to start an Outlook session:
Using early binding has two important advantages. First, code using early
binding runs faster than code using late binding (CreateObject/GetObject).
Second, because you reference the Outlook object library, you can get
online Outlook programming help using the object browser and Help system.
The Outlook Object ModelThe Outlook object model provides functionality to manipulate data stored in Outlook folders. However, there is limited functionality available to control Outlook itself. For example, you cannot use the object model to change the Options settings on the Tools menu.NOTE: As a possible workaround to limitations regarding the object model, you can use the CommandBars object provided by Microsoft Office to execute commands that are assigned to either toolbar buttons or menu commands. For example, you can use the CommandBars object to execute the New Call command (on the Dial submenu of the Tools menu) to bring up the New Call dialog box. For more information about using CommandsBars with Microsoft Outlook 98, please see the following article in the Microsoft Knowledge Base: Q182394 OL98: How to Use Command Bars in Outlook SolutionsMost programming solutions need to interact with the data stored in Outlook. Outlook stores all of its information in Messaging Application Programming Interface (MAPI) folders. Therefore, after you set an object variable to Outlook.Application, you will commonly set a "Namespace" object to MAPI:
Once you set the Namespace object, you are ready to set the next object to
a folder within the MAPI Namespace. One common way of doing this is by
specifying Outlook's "default" folders, which are the folders at the same
folder level as the Inbox that receives incoming mail. The following code
will set the objFolder object to the default Contacts folder:
For more information about referencing folders and items, please see
the following article in the Microsoft Knowledge Base:
Q182614 OL98: Programming Examples for Referencing Items and FoldersOnce you are programmatically at the folder that contains the items you want to either use or create, you must use appropriate code to accomplish your programming task. See the section below for some common programming examples. Sample Code for Common Programming TasksCreate a New Default Task Item:
Create a New Contact Using a Custom Form:
Sample Subroutine to Loop Through All the Default Contacts:
Resources for Outlook AutomationThe following list includes some important resources for automating Outlook, located on the Microsoft Outlook Developer Forum:
REFERENCESFor more information about creating solutions with Microsoft Outlook 98, please see the following articles in the Microsoft Knowledge Base: Q180826 OL98: Resources for Custom Forms and Programming Additional query words: OutSol OutSol98
Keywords : kbdta kbdtacode OffVBS |
Last Reviewed: November 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |