Aside from this one issue it appears to be working fine. We've got a couple hundred reports in the CMS and they all load without issue and navigate without issue except for refresh breaking upon print/export. This seems more to be a bug with that process than something that's not supposed to work. I know I had to replace the CrystalImageHandler class in my project due to a bug with images in reports ( read here for details: CR for VS SP09 - Embedded images not showing in... | SCN ). There are also posts elsewhere on this forum where people had similar issues with print breaking the report ( Printing with CRViewer print button freezes the ASP.NET page for example) with no resolution posted. While this might be a problem with my code or the built-in functionality, I don't believe the issue is a compatibility problem as you suggest.
↧