Hiding a Subreport: exists

Is it possible to hide a row of data if for instance no data exists in that
row. so my report isn't 300 pages long when it should just be 30?
I was looking at the visibility element but didn't see anything to hide
based on expression.
Thanks,
CJThis should be fairly straight forward to accomplish. If we assume that you
want to hide a detail row when fieldx is null you would set the visibility
on the detail row as follows:
=iif(Fields!fieldsx.Value is Nothing, true, false)
Table row visibility is exposed in the Properties window.
The attached report demonstrates this technique.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> Is it possible to hide a row of data if for instance no data exists in
> that
> row. so my report isn't 300 pages long when it should just be 30?
> I was looking at the visibility element but didn't see anything to hide
> based on expression.
> Thanks,
> CJ
>
HidingTableDetailRow.rdl
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Table Name="table1">
<Height>0.75in</Height>
<Style />
<Header>
<TableRows>
<TableRow>
<Height>0.25in</Height>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>5</ZIndex>
<rd:DefaultName>textbox1</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>Company Name</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox2">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>4</ZIndex>
<rd:DefaultName>textbox2</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>Region</Value>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
</TableRow>
</TableRows>
</Header>
<Details>
<TableRows>
<TableRow>
<Height>0.25in</Height>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="CompanyName">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>1</ZIndex>
<rd:DefaultName>CompanyName</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>=Fields!CompanyName.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="Region">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<rd:DefaultName>Region</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>=Fields!Region.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Visibility>
<Hidden>=iif(Fields!Region.Value is Nothing, true,
false)</Hidden>
</Visibility>
</TableRow>
</TableRows>
</Details>
<DataSetName>Northwind</DataSetName>
<Width>3.33334in</Width>
<Footer>
<TableRows>
<TableRow>
<Height>0.25in</Height>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox7">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>3</ZIndex>
<rd:DefaultName>textbox7</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox8">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>2</ZIndex>
<rd:DefaultName>textbox8</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
</TableRow>
</TableRows>
</Footer>
<TableColumns>
<TableColumn>
<Width>1.66667in</Width>
</TableColumn>
<TableColumn>
<Width>1.66667in</Width>
</TableColumn>
</TableColumns>
</Table>
</ReportItems>
<Style />
<Height>1.875in</Height>
</Body>
<TopMargin>1in</TopMargin>
<DataSources>
<DataSource Name="Northwind">
<rd:DataSourceID>32d95cbf-5e5b-4fb3-a37a-39b9506b8c80</rd:DataSourceID>
<ConnectionProperties>
<DataProvider>SQL</DataProvider>
<ConnectString>data source=localhost;initial
catalog=Northwind</ConnectString>
<IntegratedSecurity>true</IntegratedSecurity>
</ConnectionProperties>
</DataSource>
</DataSources>
<Width>5.00001in</Width>
<DataSets>
<DataSet Name="Northwind">
<Fields>
<Field Name="CustomerID">
<DataField>CustomerID</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="CompanyName">
<DataField>CompanyName</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="ContactName">
<DataField>ContactName</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="ContactTitle">
<DataField>ContactTitle</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Address">
<DataField>Address</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="City">
<DataField>City</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Region">
<DataField>Region</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="PostalCode">
<DataField>PostalCode</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Country">
<DataField>Country</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Phone">
<DataField>Phone</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Fax">
<DataField>Fax</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
</Fields>
<Query>
<DataSourceName>Northwind</DataSourceName>
<CommandText>SELECT *
FROM Customers</CommandText>
<Timeout>30</Timeout>
</Query>
</DataSet>
</DataSets>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>4792d607-5639-4c89-ac36-2794e9e78a74</rd:ReportID>
<BottomMargin>1in</BottomMargin>
</Report>|||Hi,
Have you tried the properties box for the row/cells? If you right-click the
row/cell in question, you can click on the Advanced button. This will bring
up several tabs, one of which will be Visibility. In the first grouping of
choices, "Initial Visibility", there is an Expression option that you could
use. I'm guessing you could enter your expression there to determine the
row/cell's initial visibility.
I'm pretty new as RS, so I'm not sure if I've helped. :)
-Kelly
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> Is it possible to hide a row of data if for instance no data exists in
that
> row. so my report isn't 300 pages long when it should just be 30?
> I was looking at the visibility element but didn't see anything to hide
> based on expression.
> Thanks,
> CJ
>|||Why was the row created, if there is no data? Perhaps you need to work on
the underlying SQL?
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> Is it possible to hide a row of data if for instance no data exists in
that
> row. so my report isn't 300 pages long when it should just be 30?
> I was looking at the visibility element but didn't see anything to hide
> based on expression.
> Thanks,
> CJ
>|||Not every report is just *simple* SQL. It's a recursive sub report...
I have a complex
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> Why was the row created, if there is no data? Perhaps you need to work on
> the underlying SQL?
>
> "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > Is it possible to hide a row of data if for instance no data exists in
> that
> > row. so my report isn't 300 pages long when it should just be 30?
> >
> > I was looking at the visibility element but didn't see anything to hide
> > based on expression.
> >
> > Thanks,
> > CJ
> >
> >
>|||Regardless, creating and then hiding blank rows implies a fundamental design
flaw. Both take unneccesary time.
Jeff
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> Not every report is just *simple* SQL. It's a recursive sub report...
>
> I have a complex
> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > Why was the row created, if there is no data? Perhaps you need to work
on
> > the underlying SQL?
> >
> >
> > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > Is it possible to hide a row of data if for instance no data exists in
> > that
> > > row. so my report isn't 300 pages long when it should just be 30?
> > >
> > > I was looking at the visibility element but didn't see anything to
hide
> > > based on expression.
> > >
> > > Thanks,
> > > CJ
> > >
> > >
> >
> >
>|||How do you figure?
Say we have a tree structure we are trying to report, such as?
Line A
-- Line B (child to a)
-- Line C (child to b)
-- Line D( child to A)
-- blank (no children)
Thats a fundamental design flaw?
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:ewPtflftEHA.1048@.tk2msftngp13.phx.gbl...
> Regardless, creating and then hiding blank rows implies a fundamental
design
> flaw. Both take unneccesary time.
> Jeff
> "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> > Not every report is just *simple* SQL. It's a recursive sub report...
> >
> >
> >
> > I have a complex
> > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > > Why was the row created, if there is no data? Perhaps you need to work
> on
> > > the underlying SQL?
> > >
> > >
> > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > > Is it possible to hide a row of data if for instance no data exists
in
> > > that
> > > > row. so my report isn't 300 pages long when it should just be 30?
> > > >
> > > > I was looking at the visibility element but didn't see anything to
> hide
> > > > based on expression.
> > > >
> > > > Thanks,
> > > > CJ
> > > >
> > > >
> > >
> > >
> >
> >
>|||This is a classic drill down. Doing a drill down you will not have any
blanks. In drill down you can set it either be expanded or not (for instance
if you wanted to show line A and they have to click on the + to expand it.
Or you can show Line A, Line B, Line D and they click on the + for Line B to
expand it.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:u4V6oSgtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> How do you figure?
> Say we have a tree structure we are trying to report, such as?
> Line A
> -- Line B (child to a)
> -- Line C (child to b)
> -- Line D( child to A)
> -- blank (no children)
> Thats a fundamental design flaw?
> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> news:ewPtflftEHA.1048@.tk2msftngp13.phx.gbl...
> > Regardless, creating and then hiding blank rows implies a fundamental
> design
> > flaw. Both take unneccesary time.
> >
> > Jeff
> >
> > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> > > Not every report is just *simple* SQL. It's a recursive sub report...
> > >
> > >
> > >
> > > I have a complex
> > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > > news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > > > Why was the row created, if there is no data? Perhaps you need to
work
> > on
> > > > the underlying SQL?
> > > >
> > > >
> > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > > > Is it possible to hide a row of data if for instance no data
exists
> in
> > > > that
> > > > > row. so my report isn't 300 pages long when it should just be 30?
> > > > >
> > > > > I was looking at the visibility element but didn't see anything to
> > hide
> > > > > based on expression.
> > > > >
> > > > > Thanks,
> > > > > CJ
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Yes a flaw, thankyou. Don't show blanks when there are no children (')
Takes time to build a blank row, and time to hide it.
Duh
Jeff
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:u4V6oSgtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> How do you figure?
> Say we have a tree structure we are trying to report, such as?
> Line A
> -- Line B (child to a)
> -- Line C (child to b)
> -- Line D( child to A)
> -- blank (no children)
> Thats a fundamental design flaw?
> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> news:ewPtflftEHA.1048@.tk2msftngp13.phx.gbl...
> > Regardless, creating and then hiding blank rows implies a fundamental
> design
> > flaw. Both take unneccesary time.
> >
> > Jeff
> >
> > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> > > Not every report is just *simple* SQL. It's a recursive sub report...
> > >
> > >
> > >
> > > I have a complex
> > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > > news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > > > Why was the row created, if there is no data? Perhaps you need to
work
> > on
> > > > the underlying SQL?
> > > >
> > > >
> > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > > > Is it possible to hide a row of data if for instance no data
exists
> in
> > > > that
> > > > > row. so my report isn't 300 pages long when it should just be 30?
> > > > >
> > > > > I was looking at the visibility element but didn't see anything to
> > hide
> > > > > based on expression.
> > > > >
> > > > > Thanks,
> > > > > CJ
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Super, thanks for being so courteous about it...
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:esNoOFitEHA.3788@.TK2MSFTNGP09.phx.gbl...
> Yes a flaw, thankyou. Don't show blanks when there are no children (')
> Takes time to build a blank row, and time to hide it.
> Duh
> Jeff
> "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> news:u4V6oSgtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> > How do you figure?
> >
> > Say we have a tree structure we are trying to report, such as?
> >
> > Line A
> > -- Line B (child to a)
> > -- Line C (child to b)
> > -- Line D( child to A)
> > -- blank (no children)
> >
> > Thats a fundamental design flaw?
> >
> > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > news:ewPtflftEHA.1048@.tk2msftngp13.phx.gbl...
> > > Regardless, creating and then hiding blank rows implies a fundamental
> > design
> > > flaw. Both take unneccesary time.
> > >
> > > Jeff
> > >
> > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> > > > Not every report is just *simple* SQL. It's a recursive sub
report...
> > > >
> > > >
> > > >
> > > > I have a complex
> > > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > > > news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > > > > Why was the row created, if there is no data? Perhaps you need to
> work
> > > on
> > > > > the underlying SQL?
> > > > >
> > > > >
> > > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > > > > Is it possible to hide a row of data if for instance no data
> exists
> > in
> > > > > that
> > > > > > row. so my report isn't 300 pages long when it should just be
30?
> > > > > >
> > > > > > I was looking at the visibility element but didn't see anything
to
> > > hide
> > > > > > based on expression.
> > > > > >
> > > > > > Thanks,
> > > > > > CJ
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Learning can be hard.
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:#l04yBqtEHA.2624@.TK2MSFTNGP11.phx.gbl...
> Super, thanks for being so courteous about it...
>
> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> news:esNoOFitEHA.3788@.TK2MSFTNGP09.phx.gbl...
> > Yes a flaw, thankyou. Don't show blanks when there are no children (')
> > Takes time to build a blank row, and time to hide it.
> >
> > Duh
> >
> > Jeff
> > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > news:u4V6oSgtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> > > How do you figure?
> > >
> > > Say we have a tree structure we are trying to report, such as?
> > >
> > > Line A
> > > -- Line B (child to a)
> > > -- Line C (child to b)
> > > -- Line D( child to A)
> > > -- blank (no children)
> > >
> > > Thats a fundamental design flaw?
> > >
> > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > > news:ewPtflftEHA.1048@.tk2msftngp13.phx.gbl...
> > > > Regardless, creating and then hiding blank rows implies a
fundamental
> > > design
> > > > flaw. Both take unneccesary time.
> > > >
> > > > Jeff
> > > >
> > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> > > > > Not every report is just *simple* SQL. It's a recursive sub
> report...
> > > > >
> > > > >
> > > > >
> > > > > I have a complex
> > > > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > > > > news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > > > > > Why was the row created, if there is no data? Perhaps you need
to
> > work
> > > > on
> > > > > > the underlying SQL?
> > > > > >
> > > > > >
> > > > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > > > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > > > > > Is it possible to hide a row of data if for instance no data
> > exists
> > > in
> > > > > > that
> > > > > > > row. so my report isn't 300 pages long when it should just be
> 30?
> > > > > > >
> > > > > > > I was looking at the visibility element but didn't see
anything
> to
> > > > hide
> > > > > > > based on expression.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > CJ
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Alright, so then I don't understand the drill down then... How does this
create a visual heirachial grouping?
does that make sense? at least in report services? I can do it in sql no
problem, just how to get reporting to respond accordinginly... curretnly,
I'm doing it with a subreport, within a sub report (that references the
parent subreport to create the recursive definition)
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:uouebyrtEHA.1272@.TK2MSFTNGP10.phx.gbl...
> Learning can be hard.
>
> "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> news:#l04yBqtEHA.2624@.TK2MSFTNGP11.phx.gbl...
> > Super, thanks for being so courteous about it...
> >
> >
> > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > news:esNoOFitEHA.3788@.TK2MSFTNGP09.phx.gbl...
> > > Yes a flaw, thankyou. Don't show blanks when there are no children
(')
> > > Takes time to build a blank row, and time to hide it.
> > >
> > > Duh
> > >
> > > Jeff
> > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > news:u4V6oSgtEHA.1216@.TK2MSFTNGP10.phx.gbl...
> > > > How do you figure?
> > > >
> > > > Say we have a tree structure we are trying to report, such as?
> > > >
> > > > Line A
> > > > -- Line B (child to a)
> > > > -- Line C (child to b)
> > > > -- Line D( child to A)
> > > > -- blank (no children)
> > > >
> > > > Thats a fundamental design flaw?
> > > >
> > > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
> > > > news:ewPtflftEHA.1048@.tk2msftngp13.phx.gbl...
> > > > > Regardless, creating and then hiding blank rows implies a
> fundamental
> > > > design
> > > > > flaw. Both take unneccesary time.
> > > > >
> > > > > Jeff
> > > > >
> > > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > > news:edGjn3QtEHA.1336@.tk2msftngp13.phx.gbl...
> > > > > > Not every report is just *simple* SQL. It's a recursive sub
> > report...
> > > > > >
> > > > > >
> > > > > >
> > > > > > I have a complex
> > > > > > "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in
message
> > > > > > news:ejERQKwsEHA.2072@.tk2msftngp13.phx.gbl...
> > > > > > > Why was the row created, if there is no data? Perhaps you need
> to
> > > work
> > > > > on
> > > > > > > the underlying SQL?
> > > > > > >
> > > > > > >
> > > > > > > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > > > > > > news:e6JtN0ssEHA.3984@.TK2MSFTNGP09.phx.gbl...
> > > > > > > > Is it possible to hide a row of data if for instance no data
> > > exists
> > > > in
> > > > > > > that
> > > > > > > > row. so my report isn't 300 pages long when it should just
be
> > 30?
> > > > > > > >
> > > > > > > > I was looking at the visibility element but didn't see
> anything
> > to
> > > > > hide
> > > > > > > > based on expression.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > CJ
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

Friday, March 23, 2012

higher compatibility level already exists

Sunday, February 26, 2012

Hiding SQL server

Hiding Rows in a Table

Hiding a Subreport

Blog Archive

About Me