|
|
Home : Search : Code Sample Library : Downloads : About : Feedback :
This list of CDO Rendering library 1.x objects and collections is compiled from the CDO.HLP file which is included on the Microsoft Exchange Server 5.5 CD-ROM. Note that an updated CDO.HLP file is included in the Microsoft Exchange Server 5.5 Service Pack 1 (or higher). You can also download the most current version from CDOLive cdo.zip(1,065 Kbyte).
| Objects | Description |
|---|---|
| RenderingApplication (Object only) | The RenderingApplication object provides a framework and support
for specific rendering objects. The RenderingApplication object provides a framework for a rendering application. You can set options on the RenderingApplication object that are inherited by all rendering objects created by the CreateRenderer method. The interface instantiated by the RenderingApplication object also provides for event logging and performance monitoring. A RenderingApplication object is considered a top-level object, meaning it can be created directly from a Microsoft Visual Basic program. In the CDO Rendering library 1.x it has a ProgID of AMHTML.Application. Note that you specify the full ProgID AMHTML.Application instead of just "Application" in order to distinguish a CDO 1.x Rendering application from other types of applications available to a Microsoft Visual Basic program through other object libraries. |
| ContainerRenderer (Object only) | The ContainerRenderer object renders the rows of a container
object as an HTML table. The ContainerRenderer object can render any subset of the rows of a container object. It can accept a CDO 1.x AddressEntries, Folders, Messages, or Recipients collection in its DataSource property. The container renderer inherits all the functionality of the object renderer, and has additional capability specific to rendering an address book container or folder as a table. You must Set the ContainerRenderer object to Nothing, or Set its DataSource property to Nothing, before you call the Session object's Logoff method. Failure to do so can result in unexpected behavior. |
| Formats (Object and Collection) | The
Formats collection object contains zero or more formats for a
rendering. A Formats collection supports count and index values that let you access an individual Format object through the Item property. The Formats collection also supports the Microsoft Visual Basic For Each statement. The Formats collection object controls how the values of certain properties are rendered. A property represented by a Format object in the collection is rendered according to the patterns in that format. Every property to be rendered can be represented by at most one Format object. |
| Patterns (Object and Collection) |
The
Patterns collection object contains zero or more patterns in a
format. A Patterns collection supports count and index values that let you access an individual Pattern object through the Item property. The Patterns collection also supports the Microsoft Visual Basic For Each statement. The parent Format object represents a property to be rendered. The Patterns collection should contain enough patterns to cover all possible values of this property. Each Pattern object's Value property indicates the set of values to be rendered by that pattern. If only one Pattern object is included in the collection, its Value property should contain a string value consisting of a single asterisk (*), which matches all possible values of the property to be rendered. |
| Views (Object and Collection) | The Views collection object contains one or more views for a
container object. A Views collection supports count and index values that let you access an individual TableView object through the Item property. The Views collection also supports the Microsoft Visual Basic For Each statement. The Views collection can contain a variety of different classes of view objects. The classes currently implemented are represented by the CalendarView and TableView objects. The Views collection is used by a ContainerRenderer object to render a container object, such as an address book container or a folder. The Views collection comes into being when a rendering application sets the container renderers DataSource property to the container object. The collection is released when the parent ContainerRenderer object is released, or when a new container object is set in the DataSource property. The various view objects initially in the collection are those that were already generated externally to the rendering application. These views persist in the underlying store, typically a directory or message store. New views can be defined and contributed to the collection using the Add method, but they do not persist after the collection is released. The view to be applied to the container object is specified in the container renderers CurrentView property. A newly instantiated Views collection always has a default current view. This default can be specified by the store underlying the container object. If it is not specified, the CDO Rendering library 1.x sets it to the first view in the collection. |
| Columns (Object and Collection) | The Columns collection object contains zero or more columns in a
view. A Columns collection supports count and index values that let you access an individual Column object through the Item property. The Columns collection also supports the Microsoft Visual Basic For Each statement. |
| ObjectRenderer (Object only) | The ObjectRenderer object renders selected properties of a
specified CDO 1.x object. The ObjectRenderer object can be applied to a CDO 1.x object to render selected properties. For example, you can use it to render the subject properties of a Message object or the subfolders of a Folder object. The object renderer is easier and faster to use than a specialized renderer such as the ContainerRenderer object. You use the object renderer when you need only a few properties and not the full tabular functionality of the specialized rendering object. You must Set the ObjectRenderer object to Nothing, or Set its DataSource property to Nothing, before you call the Session object's Logoff method. Failure to do so can result in unexpected behavior. |
The Premier Resource for
Microsoft Collaboration Data Objects