Refresh

This option updates an extract with changes made. The update can be a refresh from the parent database only (which itself may be an extract). Alternatively, if there is a hierarchy of extracts, a full refresh can be used instead, to update an extract with changes from all its ancestors. Refreshing operates on a whole database: partial operations are not possible. If changes have been made to the data in an extract, the changes will not be visible in lower extracts until these extracts are refreshed.

The difference between GETWORK, REFRESH and FULLREFRESH:

• GETWORK will get changes made to databases in the current Multiple Database (MDB).

• REFRESH will get changes made to the parent extract only of an extract in the MDB.

• FULLREFRESH will get changes made to all the extract ancestors of an extract in the MDB.

  Note:
  Full refresh updates the user view of the data with changes made at higher levels in the extract tree. However, when the user does a SAVEWORK users of extracts which are children of the extract will not be able to see your changes until they also do a refresh.