Are there any specific known reasons why a WHERE clause would be removed from the Crystal SQL statement before being sent to the database?
I am aware that the results of some Crystal formulas in the RecordSelectionFormula will not resolve properly and therefore all secondary processing has to be done at the client.
I have also done some searching and found some range parameters causing problems.
Neither of the above cases are at play here. The report was fairly simply at one point, then the owner of the company asked for some "small changes" and now about 18 months and about 20 small changes later, and it is running slow (takes 4 to 5 minutes for 6-8 pages). I looked into it and found all 80,000 plus records are returned to show only 300 or so.
I went back to look at an old one from over a year ago and it passed the WHERE clause but there have been about 3 subreports, several calculation formulas and other formatting changes done since then. The last 5 or so versions have no WHERE clause. I have no idea when the slow down was introduced as the client never mentioned it until I asked about it. I ran it recently in full and thought it was taking a long time. Their computers are faster but I still think it is too slow and should be using a WHERE clause.
So is there some sort of checklist I can use to review to see if I can clean up the report and make it run faster?
CRXI R2 and Pervasive database
TIA, rasinc