Each template registered on the server is stored in a single template table. Each row in this table holds information about a template component, such as the template database, forms, and views. The table contains complete information about the template. No part of the template is stored outside the table and referenced from within the table. As a result, a template can be persisted as a file from the Team Solutions Manager. Then, the file can be sent to other servers that have the Access Workflow Designer server components installed, imported into the Team Solutions Manager, and stored as a template in the modSystem database on the new server.
The advantage of having one table for each template is you can independently store many elements of the same type, such as forms or component files, and can access them directly. Because each component represents a row in the table, the components can be easily located and loaded from the template at run time.
A single table is used to store template information instead of many tables, because it gives you a compact tabular object that can be easily persisted using Microsoft ActiveX® Data Objects (ADO) and then shared with other users.
The server on which a template is deployed must have the same settings as the server on which the template has been built.
Caution You should not alter the template tables manually. Use the Access Workflow Designer and the Team Solutions Manager to make changes. Schema integrity is not guaranteed if you make manual changes to any solutions system tables.
The database table that stores the individual template information contains a number of columns used by the team solutions. The following table lists those columns and their data types and provides a brief description of each.
| Column | Data type | Description |
| Id | identity (int) | Unique identifier for each template component. |
| Name | nvarchar(128) | Name of the template component (for example, "IssuesAction"). |
| Caption | nvarchar(255) | Friendly name of the template component, displayed with the component (for example, "Main Issue Tracking Form"). |
| Description | ntext | Text describing the template. This information is entered when creating a new template in the Team Template wizard. |
| Type | char(2) | Object type:
|
| Value | image | A binary field that holds the value of each component (for example, the database snapshot, a data access page file, or a component file). |
| Properties | text | Reserved for user-defined properties. |