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

●
●
●
●
●
FactoryTalk Historian ProcessBook User Guide
284
linked source file. No matter how many links it has, only one version of the
linked file is stored and maintained. Using a linked file increases the file
size of a ProcessBook less than using an embedded object.
In establishing an OLE link, you may update the:
 Contents of the object dynamically whenever the source file changes
 Update the object only by manual command
To change the data in a linked file, such as which tags you have selected,
you switch to the source application and open the file. Changes are then
reflected in the container display according to the update method you
selected.
Alternatively, if you double-click the object, the source application and the
actual file open, allowing you to edit the object. If the source application
supports in-place activation, you can edit within the container window;
otherwise a source application window opens.
If you rename a ProcessBook or move it to another directory, drive, or PC,
any links from displays to source files can break. These broken links need
to be re-established if you wish to continue using them.
Should You Link or Embed?
 Embed, if you want to update the object data within the target
document or if you want to store all the source data within the
container application. This option is also better if you plan to link files
to different locations.
 Link, if you want the data to update dynamically or when you need to
minimize file size. The source application and linked files must
continue to be available.
When you link to a ProcessBook container, there is a risk of accidentally
changing the source file.