Hi:
Here in my company we have been trying to figure out (for several days
already) what is the weird reason that is doing the crystal control
viewer (crviewer.dll) act this way.
When we are previewing a report (that is using an Access Database as it
source), we call this snippet of code...
With CRViewer1
.EnableDrilldown = False
.EnableGroupTree = False
.Top = 0
.Left = 0
.Height = ScaleHeight
.Width = ScaleWidth
.Zoom (100)
.DisplayBackgroundEdge = True
.DisplayTabs = False
.ReportSource = m_crReport
.ViewReport 'Here, the VB.EXE Process jumps to 100% usage
End With
Just after we call CRViewer1.ViewReport method, the application hangs
and VB6.EXE jumps in the CPU Usage (verified through Task Manager).
There is no way to close the app (or Stop VB6), the only way to start
again is kill the process and start again... It's getting us crazy!
Here is some information about our environment
- Running on W2K
- Applied latest set of MDAC and OLEDB JET libraries (just in case it
was an Access problem) - Jet 4.0 Service Pack 8 -
- This error happens regardless whether we are in the VB IDE or if the
app is compiled.
Please, if anyone had experienced a similar problem, I would really be
thankful for your help.
Any idea would be appreciated.