I created a drill-down report from a cube in Analysis Services using the report wizard. When I preview the report, the columns are not wide enough to view the data without the data getting wrapped around to the next line (the number 51,520,384.92 does not display on a single line). When I try to change the column width and then preview the report, I get a fatal error and Visual Studio closes. I had the same problem when I tried to change the number format to display 2 decimal places and preview the report. However, the number format worked if I saved my changes before previewing the report. Unfortunately this does not work for column width. Is there a work around for this? If I can't format my reports I'll have to use another application.
I can format reports without any problems when I create them manually, but it would be nice to use the wizard for the easier reports.|||I believe this issue has been fixed in the upcoming SP1 release of SQL Server 2005.
Showing posts with label wide. Show all posts
Showing posts with label wide. Show all posts
Wednesday, March 7, 2012
Reporting Services Error After Formatting Report
I created a drill-down report from a cube in Analysis Services using the report wizard. When I preview the report, the columns are not wide enough to view the data without the data getting wrapped around to the next line (the number 51,520,384.92 does not display on a single line). When I try to change the column width and then preview the report, I get a fatal error and Visual Studio closes. I had the same problem when I tried to change the number format to display 2 decimal places and preview the report. However, the number format worked if I saved my changes before previewing the report. Unfortunately this does not work for column width. Is there a work around for this? If I can't format my reports I'll have to use another application.
I can format reports without any problems when I create them manually, but it would be nice to use the wizard for the easier reports.|||I believe this issue has been fixed in the upcoming SP1 release of SQL Server 2005.
Subscribe to:
Posts (Atom)