Article ID: 224869
Article Last Modified on 2/26/2004
APPLIES TO
- Microsoft Outlook 2000 Standard Edition
This article was previously published under Q224869
SYMPTOMS
If you implement one or more events in a custom task form, the events may not run when you assign the task to someone else.
CAUSE
This issue occurs because form-level events are not designed to run in a task request scenario.
WORKAROUND
To work around this issue, use one of the following methods:
- Have the recipient accept the task. A task is placed in the recipient's default Tasks folder. After this is done, the events run for both the task in the Tasks folder and the task request in the Inbox. For example, the Open event does not run the first time that you open the task request in the Inbox. But if you accept the task request, close it, and then re-open it, the event runs.
- Instead of assigning tasks, create a Microsoft Exchange public folder to store the tasks, and have everyone work out of the single public folder.
- If you want to programmatically assign a personal task to someone, design a custom mail message form to provide this functionality. You can use a script that is written in Microsoft Visual Basic Scripting Edition (VBScript) to programmatically create a task item and save that task item to the recipient's Tasks folder. You can use the Read event to automatically create the task without prompting, or you can add custom Accept or Decline command buttons to the form so that the user can choose whether or not to create the task.
REFERENCES
For additional information about available resources and answersto commonly asked questions about Outlook solutions, click the article number below to view the article in the Microsoft Knowledge Base:
146636 OL2000: Questions About Custom Forms and Outlook Solutions
Additional query words: OL2K OutSol OutSol2000 vbscript
Keywords: kbprb kbdswnet2003swept KB224869
