Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Triggers unregistered on entry to Report Writer or Modifier


TechKnowledge Content

When a user enters the Report Writer or Modifier in a running application, all Dexterity based triggers are un-registered from memory. When a user then chooses to go back to Dynamics or eEnteprise, the Startup scripts run for each application on re-entry. Therefore, you need to make sure that all your triggers are registered in the Startup global procedure. If you do not, those triggers will not fire for the user when they re-enter the application. The most common case where this occurs is the following. A developer registers one focus trigger in their Startup script that triggers on the Switch Company window. Then, inside that trigger, they register their remaining triggers using the user and company login information. While this technique works successfully on initial entry, or on switching companies, the triggers will not get registered again when the user enters Report Writer or Modifier and then returns to the main application.

This article was TechKnowledge Document ID:10057

↑ Back to the top


Keywords: kbnosurvey, kbmbspartner, kbmbsmigrate, kb

↑ Back to the top

Article Info
Article ID : 843668
Revision : 1
Created on : 3/25/2017
Published on : 12/29/2014
Exists online : False
Views : 91