User`s guide

Reports viewed using the DHTML viewer, the ActiveX viewer, or the Java viewer are processed using
the Page Server. These viewers do not allow users to change the page layout or locale of a report.
However, it is possible to develop custom viewer applications that provide this functionality.
When reports are processed by the Report Application Server (RAS), data is shared between users of
a report when these conditions are met:
• Users view a report using the same database logon information.
• Users view a report using the same parameters.
• Users view a report using the same locale settings.
• Users do not modify the report.
Reports viewed using the Advanced DHTML viewer (or your own custom application that permits report
viewing and modification) are processed using the Report Application Server.
6.4 Streamlining your reporting environment
Another step to ensuring that report users receive their information quickly is to assess your reporting
environment. What kind of database do you use? How is data organized within the database? How are
you connecting to the data you need to report off? How are you linking your database tables? By taking
these important considerations into account, you can significantly minimize the amount of data that
must physically travel across the network.
6.4.1 Selecting the fastest database and connection
To improve reporting performance, utilize your database to its full potential by having it do the majority
of your report processing. Ideally, Structured Query Language (SQL) databases are the most efficient
for carrying out this task.
For details on SQL databases, see Using SQL and SQL databases.
6.4.2 Using table indexes
You can also improve the way your data is organized within the database. For optimum processing
speed, report off indexed fields on your SQL database. Using table indexes is an easy way to increase
the speed of data access and to reduce the time it takes for Crystal Reports to evaluate data.
2012-03-14116
Designing Optimized Web Reports