Note If, for some reason, you do not want a database to inherit designs automatically via the nightly server task, you have two options: Do not put the template on a server that runs the nightly update task or do not set the "Database is a template" property. You can then distribute changes to the database design by using the Replace Design command, specifying the server where the template is located and selecting the template. Make sure to set the database properties so that the database does not automatically inherit the design via the nightly server task.

To convert a database to a template

1. Open the database you want to be a template and choose File - Application - Properties.

2. Click the Design tab.

3. Select "Database is a master template."

4. Enter a template name.

5. (Optional) Select "List as advanced template in 'New Database' dialog" to hide the template. Users who select "Show all templates" in the New Database dialog box can still view the template.

6. (Optional) Select "Copy profile documents with design" to propagate to databases created from the template any profile documents within the template.

7. (Optional) Select gSingle Copy Templateh to designate the template as the repository for all of the design notes. Databases that inherit from this template will store references to the design notes rather than the notes themselves.

Naming conventions

• You can use letters, numbers, and underscores in the name. Choose a name that indicates the application type or design elements represented in the template. For example, StdR6Disc represents a standard IBMR LotusR NotesR template containing the design for a Lotus Domino Designer 6 Discussion database.
• The master template name, the title, and the categories assigned to the database cannot add up to more than 99 characters.

Creating templates
Making and distributing design changes
Refreshing a design
Replacing a design
Linking a database to a template
Linking individual design elements to a template

Glossary