CrystalReportViewer AfterRender Event?

Question

We just migrated our application from VS.NET 2003 to VS.NET 2005.
Previously, we had a small dialog Show() with a timer (to show it's still processing) and a "Please want..." label.
Then we would open a form with a CrystalReportViewer control in the background. We had it disabled and minimixed.
Once Show() returned control, it would maximize the finished report and would bring the window to the front, closing the little "Please wait" window.
This allowed us to have a visible progress on report generation, especially those that ran for a minute or greater via our stored procedures.
Migrating to VS.NET 2005 broke this. Apparently as soon as CrystalReportViewer.ReportSource is set and we tell it to Show(), it will display the form before the report finishes, and return control immediately. This closes our waiting window instantly and leaves a big blank report sitting in front of the user for up to a minute.
Apparently, Crystal Reports 10 has no event that fires once a report has finished rendering. I found one available within CR11 and VS.NET 2008 titled AfterRender, but I don't even know if that will work.
So my question is--what could I possibly use to verify a report has been fully rendered/generated?

Answer 1

The main code was simply this:
Dim frmW As New frmWait
frmW.Show()
frm.crView.ReportSource = frm.rptDoc
frm.Enabled = False
frm.WindowState = FormWindowState.Minimized
frm.Show()
frmW.tmrMain.Enabled = False
frmW.Dispose()
frmW = Nothing
Me.Cursor = Cursors.Default
frm.Enabled = True
frm.WindowState = FormWindowState.Maximized
frm.crView.Zoom(1)
Where frmWait is nothing but a tiny form with the words "Please wait..." and a simple timer that shows the minutes/seconds the report has been running.
And where frmViewReport (defined as 'frm') is nothing more than a form with with a CrystalReportViewer defined as 'crView' and a ReportDocument defined as 'rptDoc'.
This code would, in VS.NET 2003, open frmW, open frm, wait for frm to finish generating the report, then frmW would Close() and frm would maximize.
This gave the effect of a nice progress timer/window for the report being generated by the application.
Now, it no longer waits for returned control at frm.Show() as it used to.
It opens frmW, opens frm, minimizes it, frmW instantly disappears, and frm maximizes and sits there with a blank report as it works on rendering/generating it.