Planning a Team Solution
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
As with all application development, planning is the key to developing successful team solutions. Wizards automate many of the processes necessary to create a Microsoft Access Workflow Designer for Microsoft SQL Server™ team solution. However, as with any other database application, the success of the team solution depends on the strength of your data model, including the relationship of tables and the workflow process.
Once the basic schema is planned, issues such as how the solution will look (the user interface), what offline capabilities are required, and how your users will interact with data and database objects must be considered.
Additionally, because these team solutions depend on security and permissions from SQL Server and the operating system, these permissions and privileges must be carefully reviewed before beginning solution development.
| For | See |
| An overview of team solution design considerations | Team Solution Development Guidelines |
| An overview of security design issues | Security Permissions Model |
| Design guidelines for selecting a database engine, Microsoft Jet, Microsoft Data Engine, and SQL Server | Database Tools and Technologies |
| Information regarding the workflow engine and design considerations | The Workflow Engine Model |
| Overview of offline replication design considerations | The Offline Replication Model |
Once your team solution is planned, you can get started with development. For more information, see Developing a Team Solution.
To develop a team solution
Register a SQL Server database as a team solution. For details, see Creating a Team Solution from a Database.
Create a table hierarchy consisting of main and details tables. For details, see Setting up a Table Hierarchy.
Create a linear workflow process using the Workflow Process wizard. For details, see Adding a Workflow Process to your Solution.
Enhance the workflow process by adding additional actions, branching transitions, and script using the workflow designer. For details, see Adding and Modifying States in a Workflow.
Add database users, and assign them to roles. For details, see Assigning Users to Database Roles.
Add role permissions, and designate the offline capability of workflow actions. For details, see Defining Permissions for Offline Publications.
Enable offline replication components, and create an offline publication. For details, see Creating an Offline Publication.
Create a Web-based user interface using data access pages. Add script necessary to take solution offline. For details, see Developing the User Interface.
Test the team solution. For details, see Testing Your Workflow.