I hope I have explained myself sufficiently.
I verify the report and the Crystal Reports design environment always indicates that there is no problem, but as I understand it, this runs in 32-bit mode anyway and the error wouldn't necessarily manifest itself there. If I create a new report that uses the same stored procedure from the same SQL Server (currently SQL2000), and I set the conditional formatting, the report works fine.Ĭlearly I don't want to have to recreate every report I have unless its really unavoidable. If I clear the formulas, the report works OK. With FastReport.Net, you can create application. Now, when I set the Target CPU to An圜PU or 圆4 ready for deployment and testing, I find that the exact same report that worked above fails, more often than not on conditional formatting with suppression or color formulas. FastReport.Net is a full-featured reporting solution for Windows Forms, ASP.NET and MVC.
This works because I set the Target CPU to x86 under Advanced Compile Options (mainly so I can debug whilst developing). I can set the properties of the viewer to the report and I can see the report content both at runtime in the IDE and running the EXE directly. From a 64-bit Windows 7 PC, I have a Visual Studio 2010 application that has a report viewer on a form.
0 kommentar(er)
