ASE Home Page Products Download Purchase Support About ASE
ChartDirector General
 Forum HomeForum Home   SearchSearch

Message ListMessage List     Post MessagePost Message

  Chart Director compatible with crystal reports 10.5 in VS. 2008
Posted by Kiran on Nov-14-2008 15:30
| Reply | Monitor
Chart Director compatible with crystal reports 10.5 in VS. 2008  for a web application.

I have problem when exporting the crystal reports which has the image that is generated by chart director. I use a dataset to bind data to a crystal report the image generated by chart director is converted in to bytes[] and passed  to the CR using the dataset the Crystal report chart is generated fine but when I try to export print or export the crystal
report I some times get an error :
Invalid report file path.
Exception Details: CrystalDecisions.CrystalReports.Engine.LoadSaveReportException: Invalid report file path.

this mostly happens in the development server the other reports which does not have the chart director image are working fine  but reports having  Chart director generated image , the export and print option some times doesn?t work .i am using the report viewer tool bar to export the report.

  Re: Chart Director compatible with crystal reports 10.5 in VS. 2008
Posted by Peter Kwan on Nov-15-2008 00:51
| Reply | Monitor
Hi Kiran,

Unluckily, I am not familiar with Crystal Reports 10.5 in VS. 2008, and so are not sure what may be the cause of the problem, or whether it is related to ChartDirector or not, or related to how the image is passed to Crystal Reports.

However, in general, the image generated by ChartDirector is indistinguishable from any other image. If your code generated the image as a PNG file, it is just the same as any PNG file to Crystal Report. If the image is generated as byte[], it is indistinguishable from any other image also generated as byte[]. So I think in theory, if this is what your code is doing, the issue cannot be related to ChartDirector.

However, if your code is not passing the byte[] to CR (eg. it is just passing the URL to get the byte[], which is different), or if it is not passing the same byte[] during display and printing, then it may be related to the cause of the problem.

(In many systems, the report printed is not the same as the report that is displayed on the web page, because the paper size is likely to be different from the browser display size. The report printed may be "recreated", and it may be possible the "recreation" is not successful to due session time out or various problems.)

For debugging, if CR supports passing the chart image as an image file on the hard disk, I suggest you may use this approach. This has the advantage that you have an image file on the hard disk as an audit log, so you can see whether the chart is generated successfully or not.

Hope this can help.

Regards
Peter Kwan