SCENARIO: I have 8 related tables in a single FM7 file, primarily using a star join. The GUI layer used for printing is a separate table which contains the many required layouts, most of which use PDFs with related fields overlaid where required, or text with merged fields. This is done to seperate data from the presentation layer, so that a change in one or more of the PDFs can easily be updated without disrupting the data.

INTENDED BEHAVIOUR: The "template" table contains many layouts but only a single record - the record to be printed. The relationship with the "template" table is via a global field; it contains the primary key of the record to be printed from the main data table. Clicking on the record to be printed takes the user to the appropriate "templates" layout and displays the directly related record, along with any other relevant but more distant related fields.

OBSERVED BEHAVIOUR: a script sets the global field in the "templates" table to the correct ID and switches to the intended "template" layout. Related fields located in the same table as the primary key update properly. Related fields from one or more table "hops" away do not update. Closing the file and re-opening it causes the more distant related fields to be properly updated and displayed.

QUESTION: Why are more distant related fields not updating immediately, but only after the file is closed and reopened?

Try adding the Refresh Window script step using the option Flush Cached Join Results. This is new with v3.

Ralph, you're goooood! :-) The Flush Cache to Disk worked.

doug

Ack - I may have spoken too soon. Will let u know after more testing. :-(