My Source is Oracle. I have some defines (just 4 or 5).

It's slow with interaction of the reports.
And - and that's what bothers me, it's not fasten then when I create the exact same Report with the Oracle source. So no difference between hyperstage and no hyperstage..


Is there in General a mentionable difference between using hyperstage in normal reports and Dashboards and Portals (not only visualizations, cause there it is really an improvement) then not using hyperstage?
Or is it really only useful in Connection with visualizations???

Thanks a lot

Isn't interaction of ActiveReports done in the end-user client? That's the whole point of ActiveReports, isn't it?

In that case, the database, Oracle or HyperStage, only comes into play for creating the ActiveReport. The interaction is done within the client; no database gets involved from that point.

Hence the lack of difference between your sources. The client (browser or mail client or some such) is the bottleneck.

Jenni do you have Infoassist+ ? If yes, then better use Visualisations for this.

Thanks @Wep5622, that seems to be the reason, and seems Logical... sadfully

@Frans: I tried the same with Visualizations, but Active Reports has more, for me important, Features...

So thanks

For large active reports, client-side performance will be mainly dependent on the amount of memory and the CPU speed of the system that the receiver of the report is using. I assume you can't very well tell your customers to plug in more memory...

Another issue may be network latency, especially on flaky wireless connections (for example in a factory full of big whirring machines causing interference).

You may be able to improve all these by reducing the amount of data you send to the report. Don't send unnecessary fields, keep your field sizes tight, use variable length fields (/AnV instead of /An), aggregate where you don't need details, etc.

Going further (and probably overboard), perhaps you can "pack" (parts of) your dataset for the report and have the report "unpack" it on the fly - but that will hit the CPUs on both ends of the line.