Hi, I have a report with four tables. There are page breaks in between each table (the Insert Page Break After this table option is selected on the first three tables). When I export this report to Excel, there are four sheets with the four tables of data on them. The 2nd, 3rd and 4th sheets all have the first row empty and its height is set to 0 so it looks like rwo 2 is the first one but row 1 is actually hidden. I need this row and would like the data to be populated in the first row and not the second. Has anyone come across this before? Thanks, Jules

As an update: I have tried reversing the the page break so that the page breaks occur Before each table - this has had not helped either. Also, I selected the Fit table on one page if possible and that did not help. All tables are right next to each other - i.e. the bottom of one table is right above the top of the other but they do not overlap. Jules

Should have included this in the first post: SQL Server 2005 - SSRS 2005 Visual Studio 2005 Professional Edition .NET Framework 2.0.50727 SP 2 Excel 2003 SP 3 Anyone hit this before?

Should have included this in the first post: SQL Server 2005 - SSRS 2005 Visual Studio 2005 Professional Edition .NET Framework 2.0.50727 SP 2 Excel 2003 SP 3 Anyone hit this before? Have you found any solution to this problem? I am facing the same problem.

I think, if there is a blank space in the report body preceeding the first report item that space will be rendered as row 1 in excel (or in any other formats for that matter). I could be wrong but it worked for me. Give it a try

This is also an issue for me. I have cleaned up the format entirely... and when I view the report within Microsoft Visual Studio, all is well. But when I export to excel, the extra row appears. Any thoughts / ideas please?

Can depend on a few things - most common are tiny discrepencies in sizing of objects that causes overlaps i.e. a table width sized at 10.0000000232434cm This can happen without user interaction - I have seen specifically sized entities spontaneously change size and show these tiny amendmnets to their dimensions. the other common issue is the transformation of points to centimetres / inches. Excel works on a different system of measurement than SSRS so when transforming sizes some discrepencies can occur - I have heard mention that sizing to anything less than 0.5cm can cause an issue.... Rendering on screen is not the same as rendering to excel so the fact that it looks ok on screen does not mean that much Other than that, 0 sized rows / columns are normally due to excel trying to fit things together so do you have borders on some cells in the top row of the table but not others? padding discrepencies in the cells? All these kind of things can cause excel to try to compensate for a perceived difference when visually there is none..Rgds Geoff