Adobe FRAMEMAKER 6.0 Manual page 251

If you are using 4th Dimension, the procedure should have the following statements:
As you process the records, you write the table data to the second include file by referring to the vTbls
variable in a SEND PACKET command. For example:
The main MIF file would have the following components:
<MIFFile 6.00> # File ID
include (template.mif) # MIF template
include (Tbls.mif) # Table instances, created by
<TextFlow
...
> # end of text flow
When a FrameMaker product opens the main MIF file, it will use the two include statements to place the
data and template information in the required order.
Creating anchored frames
You can extend the technique of writing separate MIF files to handle both tables and graphics. Like table
instances, anchored frame instances must appear in the MIF file prior to the TextFlow statement. If each
record contains a graphic or a reference to a graphics file on disk, you would create a separate text file called
AFrames.mif for only the AFrames statement. Using the technique described in the previous section, you
would insert the code for the tables in the Tbls.mif file, the graphics in the AFrames.mif file, and the main
text flow in the main text file. You use an include statement to read in the AFrames.mif file.
Remember to assign unique ID numbers in the TblID statement for each table and the ID statement for each
frame.
# the database
# Main text flow
ADOBE FRAMEMAKER 6.0 251
Examples