We are migrating from DR 7.01 to DR 8.01.
We are using DF 19.1. (Windows in this case)
In some of our report views we are using TabPages where the selection is on the first tabpage and the report is on the second tabpage.
If the user activates the second tab without actually hitting the print button we now get a ComError since the ComObject is not created.
Click image for larger version. 

Name:	DR-ComError.PNG 
Views:	53 
Size:	10.4 KB 
ID:	14827
This did not happen in DR 7.01. But I guess the comObject is created later in the process now.
So how to deal with this? The easiest solution I've com up with is adding a Activating event to the view where I put the following code:
Procedure Activating
    Boolean bCreated
    Forward Send Activating
    Get IsComObjectCreated of oMyReport to bCreated
    If (not (bCreated)) Begin
        Send CreateComObject of oMyReport
Is this the way to go? Or is there a better way?