MOD2000: The xp_modWFEval Stored Procedure Is Not Documented in Help

ID: Q238768

The information in this article applies to:

Microsoft Office 2000 Developer

Moderate: Requires basic macro, coding, and interoperability skills.

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

SYMPTOMS

In Microsoft Access Workflow Designer, the xp_modWFEval extended stored procedure is not documented in Help; however, the other xp_modWF* extended stored procedures are documented in Help.

RESOLUTION

To see a list of extended stored procedures, follow these steps:

Open the Access Workflow Designer Developer's Guide Help file.

Type xp_modWfDrop in the Type in the word(s) to search for box, and then click List Topics. Note that the "Stored Procedures" topic is displayed in the right pane of the Help window.

Switch to Microsoft SQL Server Query Analyzer where your workflow-enabled database exists.

Run sp_helpextendedproc. Note that xp_modWFEval appears in the list.

However, if you search for xp_modWFEval in Help, you cannot find it.

MORE INFORMATION

The xp_modWFEval stored procedure retrieves the workflow rules and permissions for the workflow table and evaluates whether the transition should be allowed or not. The xp_modWFEval stored procedure is called only through triggers, as demonstrated in the following steps:

Perform inserts, updates, or deletes on tables that have workflow applied to them.

Run the workflow timeout with a SQL Server Job on a scheduled basis.

Bypass the SQL Agent Timeout Job and call stored procedures (such as modExecuteLocalTimeOutEvents) directly.

The workflow engine starts if it was not previously started and receives the information from the xp_modWFEval stored procedure. The xp_modWFEval stored procedure exists in the master database. Microsoft does not support calling it directly.

Additional query words: pra

Keywords : kbdta
Version : :
Platform : WINDOWS
Issue type : kbbug