In this page of the MFC Application Wizard, indicate to what level your application provides compound and active document support. Your application must support the document/view architecture to support compound documents and document templates.
By default, the application contains no compound document support. If you accept this default, your application cannot support active documents or compound files.
Compound document support
Determines whether your application provides container support, server support, or both. For more information about this area, see:
Indicates no support for Object Linking and Embedding (OLE). By default, the application wizard creates an application without ActiveX support.
Contains linked and embedded objects.
Indicates the application can create and manage compound document objects. Note that mini-servers cannot run stand alone and only support embedded items.
Indicates the application can create and manage compound document objects. Full servers are able to run stand alone and support both linked and embedded items.
Indicates the application can be both a container and a server. A container is an application that can incorporate embedded or linked items into its own documents. A server is an application that can create Automation items for use by container applications.
Indicates whether your application supports active documents. See Active Documents for more information about this feature.
Active document server
Indicates the application can create and manage active documents. If you select this option, you must specify a file extension for your active document server in the File extension box in the Document Template Strings page of the wizard. See Active Document Servers for more information.
Active document container
Indicates the application can contain active documents within its frame. Active documents may include, for example, Internet Explorer documents, or Office documents such as Microsoft Word files or Excel spreadsheets. See Active Document Containment for more information.
Support for compound files
Does not serialize the container application's documents using the compound-file format. This option forces the loading of an entire file containing objects into memory. Incremental saves to individual objects are not available. If one object is changed and subsequently saved, then all objects in the file are saved.