Rockwell Automation FactoryTalk Historian SE ProcessBook 3.2 User Guide - Manual (Page 301)

8
●
Embedding and Linking
●
●
●
●
●
283
For more information on how to write Visual Basic scripts for use with
FactoryTalk Historian ProcessBook, click Help > FactoryTalk Historian
ProcessBook VBA Language Reference.
Object Linking and Embedding
An object application may be connected to a container application by either
embedding (page 283) or linking (page 283). The distinctions between the
two have to do with the ways in which the object is stored and updated.
Embedded Objects
Embedded objects are copied from an existing file or created and then
stored as an integral part of the container application, such as FactoryTalk
Historian ProcessBook. Using an embedded object increases the file size of
a ProcessBook significantly.
Formats not natively supported by FactoryTalk Historian ProcessBook,
such as Windows metafiles, can now be pasted from the Windows
clipboard as objects in a ProcessBook display.
To change the contents of an embedded file, double-click it. The source
application software is invoked, and you can edit the object with the source
application's commands.
ProcessBook is a time-based application. When ProcessBook is used as an
embedded object, it updates dynamically whenever you double-click it.
If you rename a ProcessBook or move it to another directory, drive, or PC,
any embedded objects in displays can still be changed as long as your
system can locate the appropriate source application software.
Linked Objects
Linked object information is not stored as a part of the destination
application. Instead, the destination file stores only the location of the