| Platform SDK: CDO 1.2.1 |
The InfoStores collection object contains one or more InfoStore objects.
| Specified in type library: | CDO.DLL |
| First available in: | CDO Library version 1.0.a |
| Parent objects: | Session |
| Child objects: | InfoStore |
| Default property: | Item |
An InfoStores collection is considered a small collection, which means that it supports count and index values that let you access an individual InfoStore object through the Item property. The InfoStores collection supports the Microsoft® Visual Basic® For Each statement. For more information on collections, see Object Collections.
Name |
Available since version | Type |
Access |
|---|---|---|---|
| Application | 1.0.a | String | Read-only |
| Class | 1.0.a | Long | Read-only |
| Count | 1.0.a | Long | Read-only |
| Item | 1.0.a | InfoStore object | Read-only |
| Parent | 1.0.a | Session object | Read-only |
| Session | 1.0.a | Session object | Read-only |
(None.)
An InfoStores collection provides access to all InfoStore objects available to this session. Each InfoStore object in turn offers access to the folder hierarchy of that message store. This is used primarily to obtain access to public and private folders.
CDO does not support methods to add or remove InfoStore objects from the collection.
In general, you cannot assume that the InfoStore object’s Name property is unique. This means that you cannot rely on the name to retrieve the InfoStore from the collection. However, you can iterate through all objects in the collection using the InfoStores collection object’s Item property, and then examine properties of the individual InfoStore objects. You can also rely on the InfoStore object’s ID property, which is guaranteed to be unique.