Restrict ing Sum(...) in Report Table Footer?

Hello,
My Report Table contains a Date Field and a numeric Value field. In the
Footer row of the table I use the Sum Aggregate function to sum up all the
values for all the rows that get displayed
=sum(Fields!CountFld.Value)
I also have an conditional Expression for the background color of each cell
in the detail row
=iif(Parameters!EndDate.Value > Fields!
CurExpireDate.Value, "Gainsboro", "White")
which changes the background color of each cell in the row (I add this IIF
expression to each field in the row).
So, if a value is in a row that is the gainsboro color, I do not want to sum
that value. Is there a way to restrict sum(Fields!CountFld.Value) ?
PseudoCode
=Sum(iif(Parameters!EndDate.Value > Fields!
CurExpireDate.Value, Fields!CountFld.Value, 0))
something like this?
Thanks,
RichWell, I tried my own pseudocode and it worked!
=Sum(iif(Parameters!EndDate.Value > Fields!
> CurExpireDate.Value, 0, Fields!CountFld.Value))
I just had to change the values around
"Rich" wrote:
> Hello,
> My Report Table contains a Date Field and a numeric Value field. In the
> Footer row of the table I use the Sum Aggregate function to sum up all the
> values for all the rows that get displayed
> =sum(Fields!CountFld.Value)
> I also have an conditional Expression for the background color of each cell
> in the detail row
> =iif(Parameters!EndDate.Value > Fields!
> CurExpireDate.Value, "Gainsboro", "White")
> which changes the background color of each cell in the row (I add this IIF
> expression to each field in the row).
> So, if a value is in a row that is the gainsboro color, I do not want to sum
> that value. Is there a way to restrict sum(Fields!CountFld.Value) ?
> PseudoCode
> =Sum(iif(Parameters!EndDate.Value > Fields!
> CurExpireDate.Value, Fields!CountFld.Value, 0))
> something like this?
> Thanks,
> Rich
>|||I used the same method, but have run into 1 problem. If the table or group
spans multiple pages, the sum fails (I get #Error). Not sure if you'll
encounter this, but I thought I would make you aware of my issue using that
method.
Michael
"Rich" wrote:
> Well, I tried my own pseudocode and it worked!
> =Sum(iif(Parameters!EndDate.Value > Fields!
> > CurExpireDate.Value, 0, Fields!CountFld.Value))
> I just had to change the values around
>
> "Rich" wrote:
> > Hello,
> >
> > My Report Table contains a Date Field and a numeric Value field. In the
> > Footer row of the table I use the Sum Aggregate function to sum up all the
> > values for all the rows that get displayed
> >
> > =sum(Fields!CountFld.Value)
> >
> > I also have an conditional Expression for the background color of each cell
> > in the detail row
> >
> > =iif(Parameters!EndDate.Value > Fields!
> > CurExpireDate.Value, "Gainsboro", "White")
> >
> > which changes the background color of each cell in the row (I add this IIF
> > expression to each field in the row).
> >
> > So, if a value is in a row that is the gainsboro color, I do not want to sum
> > that value. Is there a way to restrict sum(Fields!CountFld.Value) ?
> >
> > PseudoCode
> > =Sum(iif(Parameters!EndDate.Value > Fields!
> > CurExpireDate.Value, Fields!CountFld.Value, 0))
> >
> > something like this?
> >
> > Thanks,
> > Rich
> >|||Thanks. Not the kind of surprises I am looking forward to. Hopefully, I
won't run into that problem, but if I do, I will now know that I am not
alone. This is actually quite encouraging because I have had some seroius
heartaches with RS (2000).
"Michael C" wrote:
> I used the same method, but have run into 1 problem. If the table or group
> spans multiple pages, the sum fails (I get #Error). Not sure if you'll
> encounter this, but I thought I would make you aware of my issue using that
> method.
> Michael
> "Rich" wrote:
> > Well, I tried my own pseudocode and it worked!
> >
> > =Sum(iif(Parameters!EndDate.Value > Fields!
> > > CurExpireDate.Value, 0, Fields!CountFld.Value))
> >
> > I just had to change the values around
> >
> >
> >
> > "Rich" wrote:
> >
> > > Hello,
> > >
> > > My Report Table contains a Date Field and a numeric Value field. In the
> > > Footer row of the table I use the Sum Aggregate function to sum up all the
> > > values for all the rows that get displayed
> > >
> > > =sum(Fields!CountFld.Value)
> > >
> > > I also have an conditional Expression for the background color of each cell
> > > in the detail row
> > >
> > > =iif(Parameters!EndDate.Value > Fields!
> > > CurExpireDate.Value, "Gainsboro", "White")
> > >
> > > which changes the background color of each cell in the row (I add this IIF
> > > expression to each field in the row).
> > >
> > > So, if a value is in a row that is the gainsboro color, I do not want to sum
> > > that value. Is there a way to restrict sum(Fields!CountFld.Value) ?
> > >
> > > PseudoCode
> > > =Sum(iif(Parameters!EndDate.Value > Fields!
> > > CurExpireDate.Value, Fields!CountFld.Value, 0))
> > >
> > > something like this?
> > >
> > > Thanks,
> > > Rich
> > >sql

Restrict Date Selection

Hi All
I have a From and a To Date in a SQL Server 2005 Reporting Services Report.
How do I go about restricting the To Date so that is can't be less than the
From Date and also so the To Date is no more than 12 months greater than the
From Date?
ThanksOn Jun 24, 10:24 pm, David <D...@.discussions.microsoft.com> wrote:
> Hi All
> I have a From and a To Date in a SQL Server 2005 Reporting Services Report.
> How do I go about restricting the To Date so that is can't be less than the
> From Date and also so the To Date is no more than 12 months greater than the
> From Date?
> Thanks
If my memory servers me correctly, I think the only way to have this
kind of control of granularity (limiting dates), you will need to
create custom report parameters based on a dataset(s). Sorry that I
could not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

Restoring Merge Repolication... HELP!

Hi,
I accidentaly remove a publication, I need to restore it!!!
What Date Base I must restore?
I Restore de Distribution database and only restore de Agents but not de
publication.
restore the publication database into another database with the
keep_replication switch. Then script it out and run it in the original
database.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nicols Donoso" <Nicols Donoso @.discussions.microsoft.com> wrote in message
news:31ADDAF0-6E01-443A-891D-D33AB4EC1A67@.microsoft.com...
> Hi,
> I accidentaly remove a publication, I need to restore it!!!
> What Date Base I must restore?
> I Restore de Distribution database and only restore de Agents but not de
> publication.
>
>

restoring filegroup from different date than mdf file

Can anyone tell me what the effect would be of restoring a filegroup from an
older date than the other filegroups in the database.
The tables in the older filegroup contain fewer records than the current
one. My main concern is that the sysindexes table will still contain
reference to a greater number of records.
You would not be able to access the database until you have restore all subsequent transaction log
backups for the database until current point in time. This is better explained in Books Online...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:475C96EA-967D-4200-95ED-F1038F4488E0@.microsoft.com...
> Can anyone tell me what the effect would be of restoring a filegroup from an
> older date than the other filegroups in the database.
> The tables in the older filegroup contain fewer records than the current
> one. My main concern is that the sysindexes table will still contain
> reference to a greater number of records.

restoring filegroup from different date than mdf file

Can anyone tell me what the effect would be of restoring a filegroup from an
older date than the other filegroups in the database.
The tables in the older filegroup contain fewer records than the current
one. My main concern is that the sysindexes table will still contain
reference to a greater number of records.You would not be able to access the database until you have restore all subsequent transaction log
backups for the database until current point in time. This is better explained in Books Online...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:475C96EA-967D-4200-95ED-F1038F4488E0@.microsoft.com...
> Can anyone tell me what the effect would be of restoring a filegroup from an
> older date than the other filegroups in the database.
> The tables in the older filegroup contain fewer records than the current
> one. My main concern is that the sysindexes table will still contain
> reference to a greater number of records.