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