Setting up the Office Developer Workflow Toolbar Control on Client Computers

Article
09/14/2006

If you want to use data access pages with the Office Developer Workflow Toolbar control for the Web-based user interface of your workflow application for Microsoft® SQL Server™, you must provide a way for users to set up the toolbar control on their computers. If you are using Microsoft® Exchange 2000 Server and not SQL Server, you do not have to add any workflow components to client computers.

The Office Developer Workflow Toolbar control is packaged in a signed .cab file called modwc.cab. The .cab file is copied during server setup to https://<servername>/modweb, and a default Web page is created there that will install the toolbar control on a user's computer automatically. For more information, look at the default.htm file at the earlier URL.

If you do not want to have users visit the default automatic install page, you can have the toolbar control install from your own Web pages by manually setting the codeBase property in the HTML source code. Search for clsid:B50AC29D-6368-4B04-AFCE-1F7DA9B044E0 to see the actual <OBJECT> tag in the page source. It should look similar to the following:

<object id=ActiveXCtl0 classid=clsid:B50AC29D-6368-4B04-AFCE-1F7DA9B044E0>

You must add the codebase information to the object tag, so when users visit your Web page, the Workflow Toolbar is set up on their computers automatically. This can be done by pointing the codebase to the modweb server.

<object id=ActiveXCtl0 CODEBASE="https://<servername>/modweb/modwc.cab" classid=clsid:B50AC29D-6368-4B04-AFCE-1F7DA9B044E0>

Replace <servername> in the codebase tag address with the name of the server that has Workflow Services for SQL Server installed. Alternatively, you can move the modwc.cab file to any other location and change the codebase tag address accordingly.

Share via

See Also

Additional resources