ID: | 8700 |
Title: | Automating or Customizing the Report Destination Window |
URL: | http://blogs.msdn.com/developingfordynamicsgp/archive/2009/11/04/automating-or-customizing-report-destination-window.aspx |
Description: |
One thing about "weird" behavior when it comes to computers, is that once the explanation has been discovered, it all makes perfect sense and the computer is just being logical. The primary fact for this issue is that there are actually two different Report Destination windows:
The first Report Destination window from the runtime cannot be customized by VBA or Dexterity. You cannot add it to VBA and you cannot register a Dexterity trigger against it. The only interactions that are possible with this window are by using the VBA's SendKeys command to control using keyboard key strokes or using pass through Dexterity sanScript. The Dex.dic can be referenced as dictionary 1 with the execute() function or the unsupported method of calling Dexterity from VBA via the Continuum Integration Library. Please see the materials in the following posts for more information on these methods:
The second Report Destination window which is part of the core Dynamics.dic application dictionary and can be referenced easily by both VBA and Dexterity. I hope this explains the apparent inconsistent behavior. David |
Category: | CUSTOMIZATIONS |
Link Owner: | |
Date Added: | June 17, 2010 02:09:54 AM |
Number Hits: | 20 |