Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Report stored in history getting updated

Status
Not open for further replies.

hpl2001

Programmer
Dec 18, 2001
105
CA
Hello.

In my organization we provide report access to our users through a BOE webpage. I'm having an issue with a particular report when particular runs are being stored in the report history. When the report is later viewed from the history, some of the data is being updated. End result is that I have a report with a run last of last week with some data being updated to today.

At this point I think I've isolated the issue to one particular piece of data. Its display is being supressed using a formula that is calling a SQL expression. I'm wondering if the SQL expression is the cause of my problem. Maybe it's being updated when I open the report viewing at a later date.

Has anyone had an experience like this?

TIA.

Holly
 
I have never heard of a report in the history ever changing (the whole idea of a report instance). Now if you 'View' the report in BOE. It re-runs the report.
 
Yes, it's a poser. I'm just opening a report instance that is sitting in the history folder.

H.
 
I think the SQL expression is a possibility, since it accesses the database directly and depending upon what the SQL expression contains. I would also check formulas to make sure none of them are using currentdate or sysdate or have no upper limit to a datetime period that is being used to limit the data.

-LB
 
No currentdate or sysdate are being used. Can you think of any setting that might govern the SQL expression in terms of updating? I'm poking all around but I don't see a good candidate.
 
I don’t think there are any settings specific to a SQL expression, but I wonder if a setting like “verify database” might force some sort of updating for the report as a whole if the database has changed. I have seen something like this happen, but can’t recall what might have been the underlying cause. Maybe someone else can jump in on this.

-LB
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top