Microsoft KB Archive/107066
Article ID: 107066
Article Last Modified on 10/6/2003
- Microsoft Works 2.0 Standard Edition
- Microsoft Works 2.0a
- Microsoft Works 3.0 Standard Edition
This article was previously published under Q107066
This article contains a glossary listing of some of the more commonly used object-linking-and-embedding (OLE) terms and their definitions.
ClassName: An OLE variable that identifies the object's source application type so that the correct source application is invoked for editing. Compound Document: A document that contains many different linked or embedded objects from various other documents or applications. This is the whole basis of OLE. Embedded Object: A fully self-contained piece of data represented in the destination application as a picture. This packet of information contains all the information needed to re-create the object in its source application when edited. Destination (Client, Container): The application that receives OLE information. DocFiles: A special file system for OLE applications within the operating system. The DocFiles format allows every file to hold any number of new sub-files, which can in turn hold any number of sub-files. This tree-like structure lends itself to the compound document structure, which can have embedded objects within embedded objects. You can do this in Works 3.0 by linking or embedding a spreadsheet in a Word Processor document and then embedding that Word Processor document in another Word Processor document. Linked Object: Contains a pointer to an external file containing the information displayed by the object. Native: The data format understood by the source application. This is the data used to create and modify the object in the source application. Object: A concrete, physical instance of an object class. Object Class: A definition of the type of object. The class includes specific characteristics, such as member functions that describe the type's behavior. It also includes data, upon which the member functions operate. Presentation: The data format understood by the destination application. This is the data needed to display the object in the destination application. Source (Server): The application that provides OLE information. Static Object: These are objects that the application itself creates. For example, a Works chart pasted in as a picture or a bitmap in a word processing document is a static object because it doesn't contain references to external applications or utilities. In-Place Activation (Insitu): This is the basis for OLE 2.0 functionality. In-place editing allows you to edit an embedded object from within the destination application without having to open a separate window.
Additional query words: kbhowto meanings definition term PRIORITY2
Keywords: kbhowto KB107066