MOD2000: Incorrect Case with xp_modWFDrop and xp_modWFShutdown (238769)



The information in this article applies to:

  • Microsoft Office 2000 Developer

This article was previously published under Q238769
Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access project (.adp).

SYMPTOMS

In the Microsoft Access Workflow Designer Developer's Guide Help system, xp_modWfDrop is described as an extended stored procedure that discards information for workflow tables cached by the workflow engine, and xp_modWfShutdown is described as an extended stored procedure that stops the workflow engine.

These extended stored procedures are referenced in the following topics:
  • modWfDrop (in the "Stored Procedures Reference" section).
  • modWfShutdown (in the "Stored Procedures Reference" section).
  • Stored Procedures (in the "References" section).

RESOLUTION

These extended stored procedures are actually named xp_modWFDrop and xp_modWFShutdown. In Microsoft SQL Server, the names of extended stored procedures are case-sensitive even if you have the sort order set to case-insensitive.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

To see the proper extended stored procedure names:
  1. Open the Microsoft SQL Server Query Analyzer. Connect to the proper Microsoft SQL Server that houses the workflow-enabled solution database.
  2. Type Execute sp_helpextendedproc, and then press F5. Scroll through the results-set list. Note that xp_modWFDrop and xp_modWFShutdown are in the list (with an uppercase F), but that xp_modWfDrop and xp_modWfShutdown (with a lowercase f) are not in the list.

Modification Type:MajorLast Reviewed:7/31/2001
Keywords:kbbug kbdocerr kbWorkFlowDesigner KB238769