About Default Synchronization

Forms

In analyzing a customized form, Form Sync makes a three-way comparison between these three versions:

• The customization in the Target configuration
• The base-level version in the Target configuration
• The base-level version in the Source configuration

During analysis, Form Sync looks at component attributes, such as a component's data source or type, and form attributes, such as a form's caption or script.

If the base-level version of an attribute in the Source is:

• The same as the base-level version in the Target, Form Sync keeps the customized version of the attribute in the Target without prompting the user.
• Different from the base-level version in the Target, Form Sync does this:
  • For customizations to Basic attributes, Form Sync keeps the customization in the Target without prompting.
  • For customizations to Major attributes, Form Sync prompts you about how to handle the customization. You can keep it unchanged or replace it with the base-level version from the Source.  
  Note: For descriptions of the differences between Basic and Major customizations, see Understanding WinStudio Customizations.
• Non-existent (that is, the form or component exists in the Target but not in the Source database) Form Sync leaves the new form or component in the Target database alone.

Form Sync then replaces base-level versions of forms in the Target with base-level versions from the Source.

Global Objects

A global object is treated as a unit in synchronization - unlike a form, whose multiple specifications for component attributes and form attributes are handled individually in the merge process. The only options for handling a customized global object are to:

• Keep the customized version.
• Remove the customized version, replacing it with the new version from the Source database.

If the base-level version of a global object in the Source is:

• The same as the base-level version in the Target, Form Sync keeps any customized versions of the object in the Target without prompting you.
• Different from the base-level version in the Target, Form Sync prompts you about how to handle the customization. You can either keep the customized object unchanged or replace it with the base-level version from the Source.
• Non-existent (that is, the global object exists in the Target but not in the Source database) Form Sync keeps the new global object in the Target database.

Form Sync then replaces base-level versions of global objects in the Target with base-level versions from the Source.

Explorer

When synchronizing the Explorer:

• Form Sync replaces the Master Explorer in the Target with the Master Explorer from the Source.
• Form Sync keeps all customized Public folders and My Folders folders in the Explorer in the Target database.

Because the All Forms folder is dynamically created from the forms database, the system automatically reflects any new base-level forms from the Source database.