To distribute your team solution to others, you can create a team template and either save it as a file or save it directly to a server. By saving it to a file, you can distribute the template to different servers that contain the Access Workflow Designer server components.
Once a template is stored on the server in the template directory, you can use the administration tools to create new instances of the solution on the server. For more information about creating new solutions, see Creating a Team Solution Based on a Team Template.
You can also use templates as baselines for creating new solutions. For example, you can use the Issue Tracking solution template available in Microsoft Office Developer. After creating an instance of this solution on your development server, you can modify the solution using the Access Workflow Designer tools. You can save the modified version of the team solution as a template in the template directory. Then you can use the Team Solutions Manger to either create a new instance of the solution based on the new template or export the template to a file that can be distributed and imported into the template directory on another server.
To test your team template after developing your solution, it is recommended you import the template on a new server, create an instance of the solution, and then test the end-user experience. For more information, see Testing the Team Template.
To manage solution templates
| To | Do |
| Add a new template file to the template directory | Click Import Template from File. Browse to the location of the file, and click OK. |
| Create a template file in a different location | Select a template from the list, and click Export to File. Browse to the location where you want to save the file, enter a file name, and click OK. |
| Remove a template from the server | Select a template from the list, and click Delete. |
| Rename a template | Select a template from the list, and click Properties. Enter a new name for the template, and click OK. |
Note When you create a template, the configuration of the SQL Server where the template is made is stored in the template. If you deploy the template to a server with different configuration settings, a message will warn you of possible issues.
When developing your solution, it is important to keep these configuration issues in mind. Your development server should have the same configuration as your target servers.