Crystal 7 search time

[iceman63]

Hi all,
I'm a Crystal Rookie, but I think I have come to the right place to get help ! ...

I work with a CMMS (centralised maintenance managment system) and report monthly maintenance trends within a timber processing plant, I have written a report that details these trends and it works very well, BUT it takes well over 20 mins to populate the print preview, because it sifts through 1.5 years worth of info... I would like some help on a formula that will only look at the last 3 months instead of years... I have been trying some, but to no end.

I do hope anyone can help...

Rhys

 

[Ngolem]

I have sifted through several tens of thousands records in much less time than that. I usually try to generate a report in a maximum of one minute on large reports.

The speed of a report depends on many things.

1. Linkages of the data tables....are you linking on key fields
even though they are not used in the report?
2. Design of the report selection formula
a) Does the formula have formula variables that cannot
be pushed down to the server.
b) Are you using effective selection criteria to minimize the
number of records you are returning.
3. Design of the report itself. For example, are you
unnecessarily using subreports in your reports.

Give us more information about the report problem and we shall see why it is taking 20 mins for one report.

The information required are things like

1. The data tables and how they are linked (including type of
join)
2. A sample of your Record Selection formula or the query
used to collect the records.
3. A basic idea how your report is constructed.

Yep you have come to the right place....there are many here that can help you. Some of us disappear for a while...but come back
Jim Broadbent

 

[synapsevampire]

Good to see you back, Jim.

Rhys: The most common reason for slow reports is a record selection formula (Report->Edit Selection Formula->Record) which doesn't generate pass through the SQL to the database (check Database->Show SQL Query), so all of the processing is done within Crystal. As JIm states, there are many other potential factors.

Post your version info for Crystal and the database, the record selection, and the SQL.

Someone can probably straighten it out.

As for limiting rows, in the record selection formula, place something like:

{Orders.Order Date} > dateadd("m",-3,currentdate)

replacing orders.order date with your date field.

-k

 

[iceman63]

Thanks for the help on this problem, I have made a few changes to the formula and got it to work way faster this time around, I still have a few little bugs to deal with, so no doubt I will be back with a few more questions...

thanks again

-R