<Dd> Usually the stock implementation is used . </Dd> <Dl> <Dt> OleCacheControl </Dt> <Dd> This interface is not called by the container, but internally by the object to allow it to receive notifications of when its DataObject is running, thereby allowing it to subscribe to notifications of data changes of that object and thus allowing it to update the cached presentation properly . </Dd> <Dd> Usually the stock implementation is used . </Dd> <Dt> OleDocument </Dt> <Dd> Allows the OLE object to support multiple views of its data, as well as a few related functions . </Dd> <Dt> OleDocumentView </Dt> <Dd> A document object (an object that implements OleDocument) implements this interface for every view . It allows the caller to set the site of the object, query and set the size of the object and to show and activate it, as well as some related functions . </Dd> <Dt> OleWindow </Dt> <Dd> <Dl> <Dt> OleInPlaceActiveObject </Dt> <Dd> Called by the outermost container of an object to interact with it while it's active, e.g. to process accelerator keys in the container's message queue that are meant for the contained object . </Dd> <Dt> OleInPlaceObject </Dt> <Dd> Called by the container to activate or deactivate the object . <Dl> <Dt> IOleInPlaceObjectWindowless </Dt> <Dd> A windowless object is an object that doesn't have its own window but it instead displayed in its container's window . It is used by the container to relay messages received by the container's window that are intended for the contained object . For example, if the mouse is moved over a window, Windows places a mouse move message along with the mouse coordinates in the message queue of the window . If this window contains windowless embedded objects, the message may have to be relayed to such an object if the coordinates of the mouse - pointer are over this object . For similar reasons this interface also provides access to the object's DropTarget interface . </Dd> </Dl> </Dd> </Dl> </Dd> </Dl> <Dd> This interface is not called by the container, but internally by the object to allow it to receive notifications of when its DataObject is running, thereby allowing it to subscribe to notifications of data changes of that object and thus allowing it to update the cached presentation properly . </Dd> <Dd> Usually the stock implementation is used . </Dd>

Where can an ole object be used in base