preventing Impromptu from re-querying db every time ??

[steever]

Hi,

I have a HUGE impromptu report - spanning over 300 pages.
I have a problem about 3/4 of the way through the report.
My problem is, as i try to scroll through to see this particular section of the report, Impromptu requeries the database about every 8 or so pages. The requerying takes about a minute every time, so it would take me an hour just to see the data on this section of the report. Is there a way to see the data, as it would display on the report, without having to go through the 'wait'.

I've heard there's a way to do it through Print Preview somehow, but I couldn't get it to go.

Thx all !!

S

 

[gasman009]

I believe the control you are looking for is "Retrieve on the required rows" flag. Unchecking this should bring all the rows to the machine that is running impromptu.
*The problem is that will still take hours to run the report and probably will kill your computer and the network in between.

What you probably want to do define a more specific filter for your report.

-or -

you can create an aggregate "table" or hotfile on the impromptu side or database level.

 

[Kaiaualad]

If you build a macro to open and run the report,and insert .retrieveall in the macro, it will go ahead and get all the rows, but as gasman009 has stated, it will be very hard on the PC and network.
We installed Impromptu onto the Database server and used VNC to run large reports that require lots of detail on the same server as the Database, and we didnt kill the network,and the report ran in a quarter of the time.

 

[astra1]

Why dont you export the data in excel and do the analysis



Vish