Splicing Commands
(new to 4.0) Available as in build 4.0.0.32 or later.
If an index is changed external to the Analytica User Interface -- such as if it is modified as an expression, if its index values are computed, or if it is updated from ADE, Table definitions using that index may need to be re-written. This process is called splicing. Splicing does not always occur immediately -- Analytica is likely to wait until the table definition is required before initiating the splice operation.
Normally, the fact that definitions are being spliced, and when they are being spliced, is transparent to you as a user of Analytica. However, occassionally there are reasons you might want to force the splice to occur. If you about to save a model, and you want to minimize load time and evaluation time for users or ADE applications that use the model, then you might want to force splicing to occur before saving, so this cost won't have to be paid by people using the model later. A second concern is that there is a possibility that evaluation errors might occur when Analytica performs the splice (since some indexes and their predecessors might need to be recomputed, for example). When you initiate the splice explicitly, you can control when the errors occur.
SpliceIndex all
Forces all unspliced indexes and tables to be updated. This is equivalent to:
SpliceTable all
SpliceTable ident
Splices the table definition of ident to reflect the current values of all its table indexes. All indexes of ident are spliced, and all child tables of those indexes are spliced.
SpliceIndex ident
Forces the index identified by indent to be spliced. All child table definitions are updated, although each child table might not be fully updated, since each table might contain other unspliced indexes.
Enable comment auto-refresher