I have seen this issue come up a number of times.  Trying to automate processes which involve reports and wanting to automate the Report Destination window.  Sometimes you can add the Report Destination to Visual Basic for Applications (VBA) and sometimes the system will not add the window to VBA.  This post will explain the reason for this "weird" behavior.

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:

1. In the Dex.dic. This Report Destination window is part of the runtime engine and is opened when a report is executed without the destination being specified in the Dexterity Run Report code.
    


2. In the Dynamics.dic. This Report Destination window is used by developers to ask for report destination information in advance. This information is then passed to the report writer when the developer calls a report, usually after some sort of temp