Microsoft KB Archive/247316

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:13, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

Article ID: 247316

Article Last Modified on 8/6/2002


  • Microsoft Office 2000 Developer Edition

This article was previously published under Q247316


The fields in a workflow-enabled main table do not allow input for data entry when the solution has a defined offline subscription, the solution uses a data access page with the Workflow Toolbar control, and the solution is used online. For example, you have created a workflow-enabled solution. Within this solution, you have defined non-null workflow states that are stored in the main tableStateLookup table. Assume the defined workflow states are named One, Two, Three, and Four. In the main workflow 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 browse to this page for online use and click the New button on the Workflow Toolbar control, none of the fields are cleared or emptied to allow data entry.


The Workflow Toolbar control inadvertently enters Edit mode when you click the New button on the Workflow Toolbar control. Instead of clearing out the fields for new values, the Workflow Toolbar control leaves the field values of the current record in the fields, allowing you to modify them.


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 the modStateID modifications, enable workflow processing again, and then save the changes again.


Steps to Reproduce Behavior

  1. On the computer with the Access Workflow Designer developer components, create a table named Items in Microsoft Access 2000 with the following columns and data types:

    Column name Data type and length Allow nulls and identity
    itemID int, length of 4 Clear Allow Nulls; Select Identity. Set Identity Seed and Identity Increment values as wanted.
    descrip char, length of 10 Select Allow Nulls; clear Identity.
  2. Select itemID as the primary key for the table. Save the table and close it.
  3. Start Access Workflow Designer. Add the Items table (the table that you created in step 1) as the main table.
  4. Add workflow. Define the workflow states as One, Two, Three, and Four.
  5. On the General tab of the workflow process, click to clear the Enable workflow processing check box. On the File menu, click Save Changes to save the changes.
  6. Switch back to Microsoft Access. Press F5 to refresh the database objects.
  7. Enter one or more records in the Items table. Be sure to leave the modStateID field NULL.
  8. Switch back to Access Workflow Designer. On the General tab for the workflow process, click to select the Enable workflow processing check box. On the File menu, click Save Changes to save the changes.
  9. Create an offline publication for the solution. Designate the Items table as the main table. Allow public full permissions to the offline publication.
  10. In Microsoft Access, create a data access page based on the itemsView view. Add all fields from the view except for the rowguid field.
  11. Set the page header's UniqueTable property (on the page header's Data tab) to the Items table.
  12. Add the Workflow Toolbar control to the page.
  13. Save the page to the appropriate Web folder on the Access Workflow Designer server.
  14. From a client computer where you have installed the Access Workflow Designer client components, browse to the data access page that you saved in the previous step.
  15. Click the New button on the Workflow Toolbar control.

    Note that the fields are not cleared for data entry.

Additional query words: pra new doesn t does not

Keywords: kbbug kbpending kbworkflowdesigner KB247316