CrystalReportViewer in WPF - win32 exception on application closing

Question

Hello!
I'am using the CrystalReportViewer Control in a WindowsFormsHost control as the rest of the application is made in WPF.
If the application is closed when a Report is open, the "Visual Studio JIT" Debugger windows is opened informing me that an unhandled win32 exception occured in my application although VS 2008 Writes in the output window "The program <MyApplication> has exited with code 0 (0x0)"
This error occured only when a report document has been opened. Trying to find the error, I found out that Report.Dispose() must be called to avoid the JIT message. As WPF does not support IDisposable I had to find another way to call reportClass.Dispose() when the application is closed.
I created a private ReportClass Object to which I assign the different reports that I have created. In the constructor I add the event Dispatcher.ShutdownStarted and created the handler for the event.
private ReportClass reportClass
public void MyConstructor()
     Dispatcher.ShutdownStarted += Dispatcher_ShutdownStarted;
private void Dispatcher_ShutdownStarted(object sender, EventArgs e)
    If ( reportClass != null)
       reportClass.Dispose();

Answer 1

The oracle drivers are notoriously wobbly.  Or used to be.  I thought they had been improved though.
If you can possibly, update with later dll.
Binary chop might be your best bet to work out exactly what the issue is.
Unfortunately this is going to be hard work.
I would write a test harness to stick on a virtual server and emulate bits of your functionality.
I would probably start with just insert/update/delete to oracle in various ways.
Se if you can make it go bang with a programme you can easily experiment with.
I would also get a free subscription to ants profiler and make sure you have no memory leaks.
They can cause weird behaviour.
This is less likely though since you'd usually notice some different errors.
By the way.
You probably aren't attacking your datalayer.  That means hitting it or the like.   Something like connecting might be a better word to choose there.
Not that this is at all important.  Your customers are presumably French.
Hope that helps.
Recent Technet articles:
Property List Editing ;  
Dynamic XAML