Having a small issue with the report viewer. Currently if a user tries to export the report to a file and attempts to overwrite an existing file that is used by another process (such as, it's currently open), the Report Viewer causes an unhandled exception and crashes the app.
Is there an accepted way to handle this scenario? Looking at the code, it seems like there should be a try/catch block around the block of code in the SaveExportCommand that writes to the file system.
Is there an accepted way to handle this scenario? Looking at the code, it seems like there should be a try/catch block around the block of code in the SaveExportCommand that writes to the file system.
1 Answer, 1 is accepted
0
Hi Dave,
Kind regards,
Elian
the Telerik team
No one has reported such problem until now, we also couldn't reproduce it on our side. If saving is unsuccessful the save dialog simply does not disappear and awaits unique name (but no exceptions). We have the following questions:
- What version of Telerik Reporting are you using?
- Does the same issue appear on our online demos or is it only in your project?
- Does it happen on any machine or just on a specific one?
Kind regards,
Elian
the Telerik team
Q3’11 of Telerik Reporting is available for download. Register for the What's New in Data Tools webinar to see what's new and get a chance to WIN A FREE LICENSE!