Page 1 of 1
Chart errors in Runtime
Posted: Mon Feb 02, 2004 10:45 am
by Bryan_Singleton_(Guest)
I get an R&R Report viewer error when running a report which includes a chart in runtime mode. The error occurs when the report gets to the chart. Any preceeding listings are OK. If I run the report immediately again, I get no such error - it goes away, but if I run another report with a chart, the error occurs with that report. On returning to my original report, the error occurs again. It does not matter which version of R&R I am running - I have tried 8,9 & 10. None of my colleagues have the same problem, but it is a persistent problem. Has anybody else experienced it? I have no such problems in Designer mode. OS is XP.
=> RE: Chart errors in Runtime
Posted: Mon Feb 02, 2004 11:16 am
by kfleming
Check the version of the GSW*.* files (there are 3 of them in the windowssystem directory) and see if yours are different from those on the machines where things work correctly.______Kathleen__R&R Support
==> RE: Chart errors in Runtime
Posted: Wed Feb 04, 2004 6:51 am
by Bryan_Singleton_(Guest)
GSW*.* Versions are the same
===> RE: Chart errors in Runtime
Posted: Wed Feb 04, 2004 9:07 am
by kfleming
Then I cannot think of any explanation of what is happening...____Kathleen__R&R Support
====> RE: Chart errors in Runtime
Posted: Wed Feb 04, 2004 8:46 pm
by Nick
when using charts in RR the amount of memory available is critical -__be sure the person running the report has closed (not just minimized) other running windows apps - as the charts needs a LOT of memory...____also- my experience is that a non-chart report runs fine - but if your memory is fragmented (a normal condition after running some Windows apps) - i would even reboot and then run the RR report with charts.____if you^re running the RR runtime - make sure that the RR report designer is not just minimized as well...__(every running app uses up memory)____good luck,__nick__
=====> RE: Chart errors in Runtime
Posted: Fri Feb 13, 2004 12:13 pm
by Bryan_Singleton_(Guest)
No, that doesn^t seem to be it. It also doesn^t explain why the report won^t run the first time, but runs perfectly ok when repeated. Thanks anyway.