The base class for OLE documents that support visual editing.
Adds an item to the list of items maintained by the document.
Sets the print-target device for all client items in the document.
Causes documents to be stored using the OLE Structured Storage file format.
Returns the OLE item that is currently in-place active.
Gets the next client item for iterating.
Gets the next document item for iterating.
Gets the next server item for iterating.
Returns the primary selected OLE item in the document.
Gets the initial position to begin iteration.
Checks for blank items in the document.
Called when the document becomes visible or invisible.
Removes an item from the list of items maintained by the document.
Marks the document as modified if any of the contained OLE items have been modified.
Handles events in the Change Icon menu command.
Handles the conversion of an embedded or linked object from one type to another.
Handles events in the Links command on the Edit menu.
Sends a mail message with the document attached.
Called by the framework to update the command UI for the Edit/Change Icon menu option.
Called by the framework to update the command UI for the Edit/Links menu option.
Called by the framework to update the command UI for the Edit/ObjectName menu option and the Verb submenu accessed from Edit/ObjectName.
Called by the framework to update the command UI for the Paste Special menu option.
Called by the framework to update the command UI for the Paste menu option.
COleDocument is derived from CDocument, which allows your OLE applications to use the document/view architecture provided by the Microsoft Foundation Class Library.
COleDocument treats a document as a collection of CDocItem objects to handle OLE items. Both container and server applications require such an architecture because their documents must be able to contain OLE items. The COleServerItem and COleClientItem classes, both derived from CDocItem, manage the interactions between applications and OLE items.
If you are writing a simple container application, derive your document class from COleDocument. If you are writing a container application that supports linking to the embedded items contained by its documents, derive your document class from COleLinkingDoc. If you are writing a server application or combination container/server, derive your document class from COleServerDoc. COleLinkingDoc and COleServerDoc are derived from COleDocument, so these classes inherit all the services available in COleDocument and CDocument.
To use COleDocument, derive a class from it and add functionality to manage the application's non-OLE data as well as embedded or linked items. If you define CDocItem-derived classes to store the application's native data, you can use the default implementation defined by COleDocument to store both your OLE and non-OLE data. You can also design your own data structures for storing your non-OLE data separately from the OLE items. For more information, see the article Containers: Compound Files..
CDocument supports sending your document via mail if mail support (MAPI) is present. COleDocument has updated OnFileSendMail to handle compound documents correctly. For more information, see the articles MAPI and MAPI Support in MFC..