Re: sqr vs crystal

[Albert Howard <starbukk@concentric.net>]

The main thing to consider is can Crystal/Query handle the
requirement...you have to realize that to produce a report through the
Query link you have to be able to do all database selection in ONE SQL
statement.  This is a very binding limitation.  You didn't specify what
database you are using, but some such as SQLServer are limited to 15 tables
per join.

The extremely limited ability to do outer joins is a problem with Query
also.  With SQR you have the advantage of being able to call additional
paragraphs to bring in tables, which gets around both the 15 table join
limit as well as the outer join problem.

Additionally, the Query/Crystal method is Queries run on the client.  So
increased network traffic is an issue.

Larger reports will probably encounter some performance problems,
particularly if you try to view in a window.  Need lots of memory on the
client box.

Formatting and "pretty-printing is an arguement FOR Crystal.  Much easier
to make reports with logos and fonts etc in Crystal.

One thing that has been lost in the history of Query/Crystal is that it was
originally intended in PeopleSoft as an end user tool for ad-hoc
reporting..not really for daily production reports. Use it as such, and do
anything that is part of production streams in SQR, so you have the option
of running them on unix/mainframes to leverage performance issues.

At 06:37 AM 10/13/98 -0700, you wrote:
>Hi everyone,
>We are in the process of implementing peoplsoft financials. Our
>interfaces are ready and now a very interesting question has come up -
>
>For custom reports what criteria should we use to determine if it is
>advisable to build the reports in sqr or crystal. Any feedback will be
>appreciated.
>        Thanks in advance.
>Satnam
>(310) 380-5109
>
>
>
>
>_________________________________________________________
>DO YOU YAHOO!?
>Get your free @yahoo.com address at http://mail.yahoo.com