Developing a Team Solution

See Also

A Microsoft Access Workflow Designer team solution is a database-driven Web application based on a Microsoft SQL Server™ 7.0 database and a Web site user interface. With the Access Workflow Designer development tools, you can create a solution that takes advantage of workflow, offline replication, and integrated row-level security features. You also have the power of Access 2000 available to help design and manage the SQL Server database schema and to create data access pages for the Web site user interface.

For information about the typical development cycle, see Team Solution Life Cycle.

The basic process for developing a team solution that takes advantage of the Access Workflow Designer core features is as follows:

To develop a team solution using Access Workflow Designer

  1. Plan your team solution before starting. Numerous considerations make solution development much easier if they are addressed from the start-for example, security and schema. For details, see Planning a Team Solution.

  2. Create a SQL Server database, and open it in the Access Workflow Designer to register it as a team solution. You have two options for creating the database: starting from a database or modifying a team template. For details about creating the database, see Creating and Registering Solution Databases.

  3. Define the table hierarchy for your team solution to identify main and detail tables. For details, see Setting up Table Hierarchies.

  4. Add a workflow process to your solution. For details, see Building a Workflow Process.

  5. Define database roles using Access 2000, and assign them to workflow actions. For details, see Creating Accounts, Logins, Roles and Users.

  6. Create offline publications for your solution, so your users can work while disconnected to the server. For details, see Allowing Users to Work Offline.

  7. Create the Web site user interface. For details, see Developing the Solution User Interface.

  8. Save your solution as a template to make it available for distribution. For details, see Creating Team Templates.