MOD2000: Improper modStateID Value Displayed When NULL Workflow State Does Not Exist (247304)
The information in this article applies to:
- Microsoft Office 2000 Developer
This article was previously published under Q247304 SYMPTOMS
You find that the first non-null, defined workflow state is improperly displayed as the first record's modStateID column value in a workflow-enabled solution.
CAUSE
The Workflow Toolbar control automatically and temporarily displays the first non-null workflow state when you notice the conditions of the Symptoms section. When the record is saved, the currently displayed workflow state is also saved to the record.
This issue can occur when the solution has a defined offline subscription, uses a data access page that has a Workflow Toolbar control, and one of the following conditions occurs: - You take the solution offline and refresh the page to stay offline.
- You use the solution online, and you click the New button on the Workflow Toolbar control to add a new record.
For example, you have created a workflow-enabled solution. Within this solution, you have defined non-null workflow states stored in the
main tableStateLookup table. Assume the defined workflow states are named One, Two, Three, and Four. In the main workflow table (named main table) you add one or more rows with a modStateID of NULL. You create an offline publication with the main table as the publication's main table. When you take the created data access page that has the Workflow Toolbar control offline on a computer with the Access Workflow Designer client components installed and refresh the page to continue to work offline, the first record's modStateID column value is improperly displayed as "One," instead of the currently stored NULL.
RESOLUTION
Either change the modStateID column values to the appropriate workflow state values (before or after enabling workflow on your solution) or do not allow the modStateID column values in the main table to be NULL. If you choose to modify the modStateID values after adding workflow to your solution, you must temporarily disable workflow processing (click to clear the Enable workflow processing check box on the General tab of the solution's defined workflow), save the changes, make your modStateID modifications, enable workflow processing again, and then save the changes again.
REFERENCESFor additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
247316 MOD2000: Clicking New Workflow Toolbar Control Button Doesn't Clear Fields for Data Entry
Modification Type: | Major | Last Reviewed: | 8/6/2002 |
---|
Keywords: | kbbug kbWorkFlowDesigner KB247304 |
---|
|