JLEmlet
asked on
Freezing columns issue in SQL Server SSRS 2008
Hi all -
I have a report created in VS2008 for Sharepoint 2010. My SSRS server is integrated with sharepoint properly and reports are rendering fine. However, I have one report that is a simple Tablix with three row groups.
When I view it in VS2008, everything looks fine. However when looking at the report within the Sharepoint site the scrolling is screwed up. As you scroll down, the actual report doesn't move down very much until you get to the bottom and then it jumps from the top to the bottom.
I also can't seem to get the correct code for freezing the rows for my outer most group.
Any help is appreciated.
I have a report created in VS2008 for Sharepoint 2010. My SSRS server is integrated with sharepoint properly and reports are rendering fine. However, I have one report that is a simple Tablix with three row groups.
When I view it in VS2008, everything looks fine. However when looking at the report within the Sharepoint site the scrolling is screwed up. As you scroll down, the actual report doesn't move down very much until you get to the bottom and then it jumps from the top to the bottom.
I also can't seem to get the correct code for freezing the rows for my outer most group.
Any help is appreciated.
Are you using the scroll bar on the side or the wheel on the mouse? Does it make a difference?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Does it matter which browser you use? This is often a browser issue, can you test a few and see if it behaves better in some than in others?
ASKER
It happens on Chrome, IE 8 and IE 9.
Does the scrolling issue remain if you remove the code for freezing the rows of the outermost group?
Can you provide the code you are using for the freezing so that we can help you?
Can you provide the code you are using for the freezing so that we can help you?
ASKER
I figured out that I had deleted some of the column static groups by mistake. It resulted in very poor performance of the report. I recreated the report from scratch and all is well. Thanks.