Re: SQL Reports driving me nuts

Have you tried putting the two tablixes into seperate tablixes and utilising the column visibility of the parent tablixes? >>> Yes I tried this but the problem I outlined below is that the inner tablix adopts the recordsource of the outer. I could live with that but the second exception occurs -

Re: SQL Reports driving me nuts

Hi Stuart, Have you tried putting the two tablixes into seperate tablixes and utilising the column visibility of the parent tablixes? So essentially, what is outlined here - http://www.sqlchick.com/entries/2011/3/5/dealing-with-white-space-due-to-a-hidden-textbox-in-reportin.html But where they s

RE: SQL Reports driving me nuts

zdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Stuart Kinnear Sent: Friday, 14 December 2012 10:45 AM To: ozDotNet Subject: Re: SQL Reports driving me nuts I think the adage "if at first you don't succeed, never try again" can be applied to this probl

Re: SQL Reports driving me nuts

I think the adage "if at first you don't succeed, never try again" can be applied to this problem. No co-operation here so I've dropped it. The solution is to write separate reports for each scenario, not ideal nor elegant but it will have to do. I tried in both client side reports - Visual Studio

Re: SQL Reports driving me nuts

SSRS 2008. I think I am getting closer but still struggling. I set both tablix to the same dataset and filtered it. This way I was able to embed the two tablix within a parent tablix. But setting the row visibility did not do anything different - Arrgh ! Anyway, I've come across another article

RE: SQL Reports driving me nuts

Hey Stuart, Which version are you using? Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-b