User’s Guide : Extending EViews : Object Linking and Embedding (OLE) : Embedding vs. Linking
Embedding vs. Linking
Before continuing, it is important that we distinguish clearly between the two basic methods of using OLE to copy an EViews object to an external document:
Embedding an EViews object is akin to taking a snapshot of your object and storing it in a document along with information connecting the output to the EViews application. The embedded snapshot contains the graph or table data, which can be edited to a limited degree by reopening it from within the external application. Embedded objects need not be connected to their EViews source.
Linking an EViews object stores a reference to the information needed to rebuild the object in EViews. All data remains within EViews. Links should remain connected to their EViews source since the linked object will look to EViews and the linked data for updating when the underlying EViews data or attributes change.
The primary distinction between embedded and linked objects lies in which application owns the data. Linked objects are pointers to information that exists solely within EViews, while embedded objects are self-contained within the document. Making a choice between these methods really depends on who you consider to be the owner of the object and the types of updating that you anticipate requiring.
An object which will require periodic updating, say from new addition of data or periodic recalculation, should be pasted as a linked object. Pasting as a link fully utilizes the power of OLE by keeping the object connected to the original data.
An object whose data will not change, but might require customizing by EViews, is probably best suited to be an embedded object. The output behaves as a static picture until reopened for modification in EViews by the external application. Embedding objects means that the output is not connected to the original data, so that only a limited amount of modification is possible.
One advantage of linking objects is that your document size can be much smaller, as linked objects contain only references to the information needed to rebuild the object in EViews. The downside to linking is that a link should remain connected to its EViews source. You cannot move or delete the original workfile if you wish to have automatic updating of the object in the external document.