• Make design changes directly in an independent database on the server.

  This technique combines making and distributing design changes in one step. Use this technique only if a small group of people uses the database and it exists on only one server.

• Make design changes in a template and then use "Replace Design" to distribute the template design to the database.
• Make design changes in a master template (sometimes called a "design template"). Use the Designer server task or Refresh Design to distribute the master template design to databases that inherit their design from the master template.

  Using a master template to manage design changes is best in larger organizations where you need to control, track, maintain, and synchronize design changes in a structured way. For small organizations, using a template or a master template is a matter of preference.

This figure below summarizes the steps you take to make and distribute design changes to different types of databases.

See Also

Templates
Updating documents after redesigning a form
Refreshing a design
Replacing a design
Design synopsis
Hiding design elements
Hiding the design of a database
Preventing design changes

Glossary