Share via


Setting Up the End-User Client Computer

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.

If users want to take a team solution offline, they must have the Access Workflow Designer client components available on their computers. The client components can be installed using the Setup program on the Microsoft Office 2000 Developer CD-ROM or from the server at http://<servername>/modweb.

For information about the components required on a client computer, see End-User Client Computer Prerequisites in the Installation Prerequisites topic. To take a team solution offline, the local computer must have a data source available. For details about installing MSDE, see Installing MSDE on the Client.

The client components must be installed only once to make it possible for team solutions to be taken offline. You are not required to install new client components for each team solution.

****Important   ****The user who installs the end-user client components on a computer is the only user who can take a solution offline on that computer.

To set up the end-user client computer from the Web site

  1. From the setup location created on the server by the server installation at http://<Servername>/modWeb/default.htm, click the Install Client Components link.

  2. Select Run this program from its current location.

  3. Follow the steps in the wizard.

To set up the end-user client computer using the Microsoft Office Developer Setup program

  1. From the Microsoft Office 2000 Developer CD-ROM root directory, click Setup.exe to open the Setup wizard.

  2. On the Install Options page, select Install Access Workflow Designer and other Developer Applications.

  3. On the Component Options page, select Access Workflow Designer Tools, and click Install.

Note*   You return to the Component Options screen when installation is completed for the selected component.***

  1. When given the option, select End-User Client Run-time Components.

After installation is complete, the computer contains the run-time components required to work with a team solution offline.

Installing MSDE on the Client

If no local data source has been installed, you can install the run-time version of MSDE using the Microsoft Office Developer Setup program. However, you will have to quit Setup and install SQL Server Service Pack 1 separately.

For details about making MSDE Setup program available for users, see the following Note to Administrators.

To run MSDE and Service Pack 1 setup from your server

  1. Open the shared folder on the server. For details about setting up this folder, see the following Note to Administrators.

  2. Run InstMSDE.exe. MSDE is installed, and you are prompted to restart the computer.

  3. After restarting, open the Sqlsp\x86\setup folder from the shared location, and run setupsql.exe.

  4. Restart the computer.

Now, you can return to the Microsoft Office Developer Setup program or navigate to the Web page (http://<servername>/modWeb/default.htm) to install the client components.

Note to Administrators

The default.htm file located on http://<servername>/modWeb is installed as part of the Access Workflow Designer server components. This file contains a link to the client Setup program.

You can customize default.htm to provide information and links to additional information as required. There is a Help file associated with default.htm called ClientHelp.htm. This file provides basic information for the user. You should customize this Web page as required.

For those using MSDE, you should provide instructions for installing it on this Web page. Before users can install MSDE, however, you must make it available on the server.

To make MSDE installation available from the server

  1. Create a shared folder on the server, and grant it public permissions.

  2. From the Microsoft Office 2000 Developer CD-ROM root directory, copy the Msde and Sqlsp folders, the InstMSDE.exe****file, and MSVBVM60.dll to the shared folder.