This method flushes cached changes to the Repository database.
Unless you have set the exclusive-write-through-mode transaction option, changes that you make within the scope of a transaction are cached, and are not written to the database until the transaction is committed. If a concurrent SQL query is run against the Repository database, the result of the query will not reflect the uncommitted changes. (This is normally the desired behavior.)
If your Repository application must be able to see uncommitted changes in SQL queries, you can use the Flush method to write uncommitted changes to the Repository database. All changes made within the scope of the current transaction are flushed. Flushing uncommitted changes does not affect your ability to cancel a transaction via the Abort method.
Call object.Flush
The Flush method syntax has these parts:
| Part | Description |
| object | The RepositoryTransaction object for the currently open Repository instance. |