CR08, vb.net 08, winform, NullreferenceException PageControl.OnMouseMove

[#1]

My environment: Win7, CR08, vb.net 08, winform application.

This has been reported in the past for CRVS10 but this is happening on a machine with just CR08, vb.net 08, winform.

I see this problem only when doing a drill-down within a drill-down.

The top of the crash stack shows this error:

-

---

System.NullreferenceException: Object reference not set to an instance of an object.

at CrystalDecisions.Windows.Forms.PageControl.OnMouseMove(MouseEventargs e)

-

---

The exception is being thrown not in my app code but in the internal Crystal Viewer code:

Using debug mode to trap what's going on, here are the internal steps where the error occurs:

-

---

Step into: Stepping over non-user code 'CrystalDecisions.Windows.Forms.PageView.DrillDownOnGroup'

Step into: Stepping over non-user code 'CrystalDecisions.Windows.Forms.PageControl.DrillDownSection'

Step into: Stepping over non-user code 'CrystalDecisions.Windows.Forms.PageControl.OnDoubleClick'

Step into: Stepping over non-user code 'System.Windows.Forms.Control.WmMouseUp'

Step into: Stepping over non-user code 'System.Windows.Forms.Control.WndProc'

Step into: Stepping over non-user code 'System.Windows.Forms.NativeWindow.DebuggableCallback'

Step into: Stepping over non-user code 'System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop'

-

---

If I insert a break point inside the code at the point where the viewer drill event occurs, the problem goes away. So perhaps this is related to the viewer having or not having the focus. If I remove all custom code from the drill event, the error still occurs (on drill-down within drill-down).

A web search on this error shows up a few similar incidents. I suspect this is a situation where a mouse move event within the viewer runtime component is not being handled properly.

I don't plan to pursue a paid incident for this. I just hope this combines with other posts to draw the attention of the development team.

[Former Member · Accepted solution]

Hi Ido,

Did you ever find a resolution to this problem? In our firm it's happening on a few machines, but I cannot seem to duplicate itas if they reload the program, it'll start working, then stop a few times later.

Thanks

[ido_millet · Accepted solution]

Hi Nathan,

No, the issue is still not solved. I believe it's simply a bug that should be resolved by trapping and handling that situation within the Crystal runtime components. Perhaps if more people report it the Crystal development team will take notice...

[former_member11696 · Accepted solution]

Hi Guys,

Sorry, I saw this post a while ago but got side tracked on other issues to get back to it.

Ido, I believe you have my e-mail address, if you want to put together simple app that duplicates the problem please do so and I'll create the track and send it off to R&D. Use one of our sample reports if you can or send me a simple report with saved data.

Also, have you installed Fix Pack 3.3 to see if that fixes the issue?

Thanks

Don