Distributing the Toolbar with an Application
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.
The Microsoft® Office XP Developer Workflow Toolbar control is packaged in a signed .cab file called modwc.cab. The .cab file is copied during server setup to http://<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="http://<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.
If you are building templates, include the .cab file in your Web site, and use a relative URL for the codeBase property to make sure links to the .cab file are correct when an instance of an application is created from the template.
See Also
SQL Server Workflow Toolbar Control | Workflow Toolbar Features | Workflow Toolbar Object Model | Scripting with the Workflow Toolbar