Well, FM doesn't have "spot cross-reference", and even if it did, it might not allow an entire table to be treated as a source. Cross-reference by <$paratext> also doesn't pull in any anchored frames from the source.
There are a number of ways you could approach this, but which is optimal depends on the table complexity, and whether you need to have deep links into it.
- For a really small table, the cell contents could all be Variables.
- For a simple table, it could be defined at one location in the Body flow (or on a Reference Page), and the table structure could be replicated as needed, with the clone contents, cell-by-cell, being Xrefs by paratext to the master cells at the defining instance.
- For a more complex table, it could be defined in an external file.fm, and imported as a Text Inset.
- A way I used to do it was to create and maintain the tables in an external spreadsheet (LibreOffice/OpenOffice Calc), exported to PDF, and imported in an Anchored Frame.
And it wouldn't be FM if there were only 4 ways to do it. And that's just for Unstructured Frame. In Structure, there may be further options, some much more elegant.
AdChoices