Document class objects, created by document-template objects, manage the application’s data. You will derive a class for your documents from one of these classes.
Document class objects interact with view objects. View objects represent the client area of a window, display a document’s data, and allow users to interact with it. Documents and views are created by a document-template object.
The base class for application-specific documents. Derive your document class(es) from CDocument.
Used for compound document implementation, as well as basic container support. Serves as a container for classes derived from CDocItem. This class can be used as the base class for container documents and is the base class for COleServerDoc.
A class derived from COleDocument that provides the infrastructure for linking. You should derive the document classes for your container applications from this class instead of from COleDocument if you want them to support links to embedded objects.
Maintains the list of OLE client items that are in the rich edit control. Used with CRichEditView and CRichEditCntrItem.
Used as the base class for server-application document classes. COleServerDoc objects provide the bulk of server support through interactions with COleServerItem objects. Visual editing capability is provided using the class library’s document/view architecture.
Related Classes
Document class objects can be persistent — in other words, they can write their state to a storage medium and read it back. MFC provides the CArchive class to facilitate transferring the document’s data to a storage medium.
Cooperates with a CFile object to implement persistent storage for objects through serialization (see CObject::Serialize).
Documents can also contain OLE objects. CDocItem is the base class of the server and client items.
Abstract base class of COleClientItem and COleServerItem. Objects of classes derived from CDocItem represent parts of documents.