Tài liệu Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution ppt

Contents Overview 1 Introduction to CDO 2 Using the CDO Library in Collaborative Applications 12 Working with Messages and Message Properties 20 Working with the CDO Object Model 29 Using the CDO Rendering Library in Collaborative Applications 46 Lab A: Adding CDO Code to the Employee Move Form 53 Review 58 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  1999 Microsoft Corporation. All rights reserved. Microsoft, Active Desktop, Active Directory, ActiveX, BackOffice, Developer Studio, FrontPage, JScript, MSDN, MSN, NetMeeting, Outlook, PivotChart, PivotTable, PowerPoint, Visual Basic, Visual C++, Visual FoxPro, Visual InterDev, Visual J++, Visual SourceSafe, Visual Studio, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Other product and company names mentioned herein may be the trademarks of their respective owners. Project Advisor: Janet Wilson Project Lead and Instructional Designer: Anne Bockman (Excell Data Corporation) Instructional Designers: Josh Barnhill (Volt Technical) and Jo Berry (Exchange) Lead Program Manager: Greg Bott Program Managers: Colleena Carr and Chris Boar (Intl Vendor) Graphic Artist: Andrea Heuston (Artitudes Layout and Design) Editing Manager: Lynette Skinner Editor: Jennifer Kerns (S&T Onsite) Copy Editor: Shari G. Smith (R & S Consulting) Online Program Manager: Arlo Emerson (Aditi) Production Support: Irene Barnett (Barnett Communications) Manufacturing Manager: Bo Galford Manufacturing Support: Mimi Dukes (S&T Onsite) Development Services: Kimber Dodge Lead Product Manager: Mary Larson Group Product Manager: Robert Stewart Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution iii Instructor Notes Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution This module presents Collaboration Data Objects (CDO) as a tool for building collaborative applications within Microsoft ® Outlook ® 2000. At the end of this module, students will be able to determine when CDO is an appropriate development tool. They will be able to distinguish among the CDO Library, the CDO Rendering Library, and the CDO for NTS Library (Collaboration Data Objects for Windows NT ® Server), and determine when it is appropriate to use each library. They will be able to use the CDO libraries to enhance the performance of their applications and to perform programming tasks that are not available by using the Outlook object model. Materials and Preparation This section provides you with the materials and preparation needed to teach this module. Materials To teach this module, you need the following materials:  Microsoft PowerPoint ® file 1593a_12.ppt  Module 12, “Integrating Collaboration Data Objects within an Outlook 2000 Solution” Preparation To prepare for this module, you should:  Read all the materials for this module.  Read the instructor notes and margin notes for the module.  Complete the lab.  Rehearse the demonstrations. Presentation: 90 Minutes Lab: 45 Minutes iv Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Module Strategy Use the following strategy to present this module:  Introduction to CDO Provide an overview of CDO technology. Explain when it is appropriate to use CDO rather than the Outlook object library. Explain the functionality and uses of the CDO Library, CDO Rendering Library, and CDO for NTS Library. Compare the capabilities of the CDO libraries. Explain how to determine which CDO library to use for particular programming tasks. Describe how to install the CDO Library and the CDO Rendering Library.  Using the CDO Library in Collaborative Applications Provide an overview of the CDO Library hierarchy and a summary of the CDO Library object functions. Compare the most commonly used objects of the CDO library with their counterparts in the Outlook object library. Explain how to create a Session object both from within Outlook 2000 and with dynamic profiles.  Working with Messages and Message Properties Explain how to select recipients from an address book. Explain how to filter and find messages in a folder. Explain how to access hidden messages in a folder. Explain how to retrieve values by using the Fields collection.  Working with the CDO Object Model Explain how to create a new address book entry. Describe how to return free/busy information and organize a meeting by using CDO. Describe how to organize a meeting, access the Organizational Forms Library, and. Explain how to avoid the common RootFolder problem in a Microsoft Windows NT service. Demonstrate the use of CDO with the Favorites folder.  Using the CDO Rendering Library in Collaborative Applications Provide an overview of the CDO Rendering Library object hierarchy and the rendering process. Explain how to display a ContainerRenderer object within a folder home page. Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 1 Overview  Introduction to CDO  Using the CDO Library in Collaborative Applications  Working with Messages and Message Properties  Working with the CDO Object Model  Using the CDO Rendering Library in Collaborative Applications At the end of this module, you will be able to:  Determine when Microsoft ® Collaboration Data Objects (CDO) is an appropriate technology for creating collaborative applications.  Distinguish between the CDO Library, the CDO Rendering Library, and the CDO for NTS Library (Collaboration Data Objects for Windows NT ® Server), and determine when it is appropriate to use each library.  Use the CDO libraries to filter messages in a folder, to access hidden messages, and to retrieve values from messages by using the Fields collection.  Use the CDO libraries to enhance the performance of your applications and to perform programming tasks that are not available by using the Microsoft Outlook ® object model.  Use the CDO Rendering Library in your collaborative application. Slide Objective To provide an overview of the module topics and objectives. Lead-in In this module, you will learn about using CDO as a tool for building collaborative applications. 2 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution    Introduction to CDO  Overview of CDO Technology  Determining When to Use CDO  Functionality and Use of CDO Libraries  Comparison of CDO Libraries  Determining Which CDO Library to Use  Installing the CDO and CDO Rendering Libraries CDO is a technology that enables you to build messaging and collaborative applications that make use of the information and capabilities of Microsoft Exchange Server 5.5 Service Pack 1. Slide Objective To outline this topic. Lead-in It is important to know what CDO is, what functionality it can provide, and to recognize its common components. Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 3 Overview of CDO Technology  Function of CDO  Consists of a library of objects, properties, and methods  Programming interface to MAPI  Use in conjunction with the Outlook object model  Versions of CDO  Version 1.0: (previously called OLE Messaging)  Version 1.1: (previously called Active Messaging)  Version 1.21: (current version; available with Outlook 2000 and Exchange Server 5.5 Service Pack 1) The primary functions and versions of CDO are described in the following text. Function of CDO CDO is a library of objects, properties, and methods that provide a programming interface to MAPI. As an interface, CDO simplifies many of the programming tasks associated with the development of collaborative applications by providing programmatic access to Exchange Server information. You can use CDO in conjunction with the Outlook object model in collaborative applications based on Outlook 2000 and Exchange Server. Within both applications, you can accomplish many functions of CDO by using the Outlook object model. However, CDO provides capabilities beyond those exposed by the Outlook object model. In addition, there are some cases in which using CDO, rather than equivalent functions of the Outlook object model, will result in better performance. Versions of CDO Different versions of CDO are recognized by different names. It is useful to be aware of the previous versions as many Knowledge Base articles and other technical publications make reference to the previous version names. These articles can contain content that is still valid for the current version of CDO.  Version 1.0. This version was called OLE Messaging.  Version 1.1. This version was called Active Messaging.  Version 1.21. The current version, CDO 1.21, is available with Outlook 2000 and with Exchange Server 5.5 Service Pack 1. Slide Objective To list the versions of CDO. Lead-in MAPI is exposed through the interfaces of CDO. 4 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Determining When to Use CDO  Using CDO to Access Advanced Features or Information  CDO is used to access information and features that are not available by using the Outlook object model  For example, use CDO to access a MAPI field that is not available by using the Outlook object model  Using CDO to Improve Performance  CDO is an in-process .dll and supports less functionality on each object than Outlook 2000  For example, use CDO to iterate quickly through a large collection of messages There are two main reasons for using CDO within an application that is based on Outlook 2000. Using CDO to Access Advanced Features or Information There are many cases in which you can use CDO to access information and features that are not available by using the Outlook object model. For example, you can use CDO to access a MAPI field that is not available by using the Outlook object model. CDO provides a Fields collection that enables a MAPI field value to be returned by passing the MAPI field tag to the Fields collection. As another example, CDO provides an Address dialog box in which users can select recipients from the available address books and have the selected recipients returned as a Recipients collection. To provide the same functionality by using the Outlook object model, you would have to create and program a custom dialog box. Using CDO to Improve Performance There are many cases in which you can use a function of CDO, rather than a similar function of the Outlook object model, to improve the performance of that function. For example, if your application needs to iterate through a large collection of messages (and it is not possible to use the SetColumns method available to Outlook 2000) the application will iterate more quickly if you use CDO rather than Outlook 2000. Slide Objective To describe the situations when CDO should be used in place of other technologies. Lead-in Use CDO when you need to access information that is not exposed by the Outlook object model, or when you need to improve performance. Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 5 Functionality and Use of CDO Libraries  CDO Library  Exposes the most common programmable messaging objects of MAPI  CDO Rendering Library  Enables you to display information from Exchange Server in a browser by using HTML  CDO for NTS Library  A separate library that is not used to access information from Exchange Server  Useful for performing bulk mailing operations without authentication CDO includes two libraries—the CDO Library and the CDO Rendering Library. A third library—the CDO for NTS Library—is also available. CDO Library The CDO Library (Cdo.dll) implements the most common programmable messaging objects of MAPI and exposes them to you. These objects include folders, messages, recipient addresses, attachments, and other messaging components. This functionality makes it easier for the developer to create, maintain, and debug messaging code. CDO Rendering Library The CDO Rendering Library (Cdohtml.dll) also exposes programmable messaging objects and other messaging components. This library enables you to display information from Exchange Server in the browser by using Hypertext Markup Language (HTML). Although the CDO Rendering Library and the CDO Library are separate, they are complementary. Specifically, the CDO Rendering Library generates HTML output from CDO Library objects and properties over the Internet. Because the CDO Rendering Library works with Microsoft Internet Information Server to generate HTML output, the corresponding .dll file is located on the server and not on the client computer. Slide Objective To list and describe the three CDO libraries. Lead-in CDO provides three different libraries that you can use depending on the requirements of your application. 6 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution CDO for NTS Library The CDO for NTS Library (Cdonts.dll) is separate from the CDO and CDO Rendering libraries. The CDO for NTS Library is intended as a streamlined alternative for a frequently used subset of these tasks. It operates independently of the other two libraries. It is not used to access information from Exchange Server, but it is useful for performing bulk mailing operations without authentication. The CDO for NTS Library is functionally compatible with a subset of the CDO Library version 1.2.1, and with a subset of the Active Messaging Library version 1.1. If an application has been written for either of these libraries, some modifications are usually required to run it with CDO for NTS. Some features of Active Messaging, such as fields, folders, and address lists, are unavailable in CDO for NTS. [...]... of Outlook 2000 A standard installation of Outlook 2000 will not include the CDO Library (version 1.21) When you install Outlook 2000, you can select a custom installation and specify that the CDO Library be installed Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 11 Installing the CDO Library After Outlook 2000 Is Installed To install the CDO Library if Outlook 2000. .. property 16 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Comparison of CDO and Outlook Objects Slide Objective CDO Object No corresponding Outlook 2000 object Folder MAPIFolder Messages Items Fields UserProperties This collection within Outlook 2000 enables you to access user-defined fields, but not all MAPI fields as the CDO Fields collection does AddressList Within. .. many objects and properties, which enable you to accomplish a wide variety of programming tasks as you develop a collaborative solution Some of the more common uses of CDO include adding a new member to the Outlook 2000 Address Book, planning and organizing a meeting, or accessing the Organizational Forms Library to open forms 30 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000. .. can select recipients You can also use CDO to access hidden messages and MAPI properties that are not available when using other technologies, such as the Outlook object model Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 21 Selecting Recipients from the Address Book Slide Objective To show examples that use CDO to display the Address Book dialog box in Outlook 2000. .. Fields collection does AddressList Within CDO, you can use the Fields collection on this object AddressList AddressEntry Within CDO, you can use the Fields collection on this object AddressEntry Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 17 Creating a Session Object Slide Objective To show how to create a new Session object and then use the Logon method Lead-in... from server and mailbox name strProfileInfo = strServer + vbLF + strMailbox Set cdoSession = CreateObject("MAPI.Session") cdoSession.Logon "", "", False, True, 0, True, _ strProfileInfo End Sub 20 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Working with Messages and Message Properties Slide Objective To outline this topic Lead-in You can use the CDO objects to work... server-based custom e-mail agents 9 10 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Installing the CDO and CDO Rendering Libraries Slide Objective To list the different ways to install the CDO Library and the CDO Rendering Library Lead-in The CDO Library is installed with Microsoft Office The version of Office and how you install it dictates the manner in which the CDO Library... address book They also allow you to force users to resolve any ambiguous names they type 22 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Displaying an Address Book with One Button Enabled The following example displays an address book with only the To button enabled, the caption of the address book titled To Only, and the text on the To button labeled Select To On Error... counted binary when you write to the field 28 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution Accessing Custom Properties You can also extend the properties available through MAPI by defining your own properties These user-defined properties, defined by using a name and automatically assigned an identifier greater than &H8000 by CDO, are called “named properties.”... collection Enables you to access public folders and personal folder store (.pst) files Folder object The Folder object is an immediate child of the Session object and is only used to gain access to the Inbox or Outbox It has as an immediate child object: the Folders collection Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution 15 (continued) Name Typical uses Messages . Instructor Notes Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution This module presents Collaboration Data Objects (CDO) as. important to have an understanding of the CDO object hierarchy structure. 14 Module 12: Integrating Collaboration Data Objects Within an Outlook 2000 Solution