Possible bug in RS -Using the Now function in expression in a Snap -- sql server reporting services

sql server reporting services : Possible bug in RS -Using the Now function in expression in a Snap

dbconsulting
4/1/2005 1:17:02 PM

We have created a report that creates a historical snapshot. In the header,
we use the Now vb function to return the current date/time. However, the Now
function does not evaulate at the report execution time. Rather, it seems to
evaluate upon the first opening of the report for viewing. Thus, the snapshot
might have been taken yesterday, but if I open the report in a browser (for
the first time) today, the Page Header now says today (and will always say
that).

Additionally, when you export the report to Excel, the Now evaluates
again... so you get the current date/time in the page header of the Excel
cell.

I will try using the Execution time to get around this, but thought I'd pass
this along.

Brian Welcker [MSFT]
4/1/2005 4:18:56 PM

Currently, page headers and footers are calculated at rendering time. This
is so that we can recalculate the page numbering when the report is
repaginated. In SQL 2005, we will change this so that the HTML and GDI
renderers will do this at processing / snapshot time while page oriented
formats will do this at rendering time. In a future version, we will change
these to be static as well.

--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services

This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]

Suneet
4/2/2005 10:17:01 AM

Well said by Brian. In case you really wanna show snapshot date/time in page
header do the following-
1. Make textbox named as TextBox1 in report and make it invisble. now put
=now as expression in it.
2. In page header make new text box and use expression =
ReportItems!TextBox1.Value

Above code works cause reportItems collection is evaluated and rendering
time but it picks the value from TextBox1 which was processed at the time of
snapshot creation.

Problem solved! :o)

-Suneet Mohan

[quoted text, click to view]

Matthew Brown
4/4/2005 8:55:19 AM

Why not use Globals.ExecutionTime ?

On Fri, 1 Apr 2005 13:17:02 -0800, dbconsulting
[quoted text, click to view]

Robert Bruckner [MSFT]
4/4/2005 11:02:50 AM

Yes, using =Globals.ExecutionTime instead of =Now would be the right
solution.

-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server reporting services

home · blog · groups

Questions? Comments? Contact the dn