Refresh Window

Updates the entire contents of the active window, including any related records.

Options 

• Flush cached join results deletes the results of queries for related records and causes related records to be refreshed. Do not select this option if you know your script does not affect related data, and if you want to minimize the performance impact of re-accessing related data (particularly when sharing a database over a network).
• Flush cached external data deletes the results of queries for related ODBC data source records and causes related ODBC records to be refreshed. FileMaker Pro empties the internal cache and refreshes record data. Do not select this option if you know your script does not access ODBC data.

Originated in version 

6.0 or earlier

Description 

This script step updates the entire contents of the active window, including any related records, and updates the visibility state of all objects with hidden conditions in the window. Refresh Window also resumes updating the active window after a Freeze Window script step.

You do not need to select Flush cached join results in order to refresh the entire window.

This script step updates records (rows) in the current ODBC table.

Notes 

• To update a single layout object without updating the entire window, use the Refresh Object script step.
• In FileMaker WebDirect, this script step closes all open popovers.

Example 1 

Updates the Total field to include taxes and beeps after all records are updated.

Go to Record/Request/Page [First]
Loop [ Flush: Always ]
    Set Field [Invoices::Total; Invoices::Total * Invoices::Tax]
    Go to Record/Request/Page [Next; Exit after last: On]
End Loop
Refresh Window [ ]
Beep

Related topics 

• Script steps reference
• Updating data between FileMaker and ODBC data sources