Article ID: 929211 - View products that this article applies to.
This article describes the rules that are used to maintain alternate windows when you make customizations in Dexterity in Microsoft Dynamics GP.
When you make customizations in Dexterity in Microsoft Dynamics GP, you may have to change existing windows in the core Dynamics.dic dictionary. These modified windows become alternate windows when they are transferred to the extracted dictionary. The windows are transferred when a chunk file is created. In alternate windows, scripts may be added to existing fields, windows, or form events.
You can experience difficulty when you maintain an alternate window because you cannot easily know what scripts have been added to the window. If the window changes significantly between versions, you may have to remake the changes that you made to the original window. If a previous script change is not maintained, the code may not work correctly.
To make it easier to maintain an alternate window, follow these rules:
Note We recommend that you avoid having alternate windows because you can have only one alternate version of a window active at a time. If two customizations have alternate versions of the same window, only the window that is set up in the Security window will be active. To avoid having alternate windows, use triggers or a synchronized third-party window.
For more information about how to create a chunk file from a development dictionary, click the following article number to view the article in the Microsoft Knowledge Base:
894700For more information about how to check whether an alternate window is in use, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/894700/ )How to create a chunk file in Great Plains 8.0 Dexterity
(http://support.microsoft.com/kb/850482/ )Referring to third party fields in focus triggers
Article ID: 929211 - Last Review: July 14, 2012 - Revision: 3.0
Contact us for more help