Active TopicsMemberlistSearchHelpRegisterLogin

Report Design
 Crystal Reports Forum : Crystal Reports 9 through 2022 : Report Design
Message Icon Topic: Restricting rows processed Post Reply Post New Topic
Author Message
RayDauhgerty
Newbie
Newbie


Joined: 07 Oct 2010
Online Status: Offline
Posts: 2
Quote RayDauhgerty Replybullet Topic: Restricting rows processed
     Posted: 07 Oct 2010 at 6:41am
I am designing a report using a main view that has 50000+ records, that uses a subreport that also uses a large view.  Normally, the user would use filter criteria that limits the report to a small set of data.  However, if they don't enter filter criteria, it either hangs the system, or if they don't enter enough filter criteria, it can take several minutes to run.
 
How can I restrict the main report to not process more than 500 rows?  So far, my attempts to use suppression formuals in the sections have only led to that particular section being suppressed, but it still takes the same time to run the report.
 
Thanks,
Ray Daugherty
IP IP Logged
DBlank
Moderator
Moderator


Joined: 19 Dec 2008
Online Status: Offline
Posts: 9053
Quote DBlank Replybullet Posted: 07 Oct 2010 at 8:00am
can you use a SQL stored proc with params as your source?
That will limit the data before it is retreived rather than after it is retrieved like the crystal select statment does.
IP IP Logged
RayDauhgerty
Newbie
Newbie


Joined: 07 Oct 2010
Online Status: Offline
Posts: 2
Quote RayDauhgerty Replybullet Posted: 07 Oct 2010 at 8:37am
No, the Crystal report is being invoked from another application, which is where the prompting for params is occuring.  The application is using a program interface to drive the report, so I don't know of a way to use a stored proc as you suggest.
Ray Daugherty
IP IP Logged
DBlank
Moderator
Moderator


Joined: 19 Dec 2008
Online Status: Offline
Posts: 9053
Quote DBlank Replybullet Posted: 07 Oct 2010 at 8:53am

The only other trick i can think of would be if you know logically on the params entered what constitutes OK or not OK before the data is retrieved. If so post this if you want help with it.

Otherwise you can suppress the whole report based on a record count and give the user a text box back saying they screwed up but it still allows for the report to run and retrieve the data.


Edited by DBlank - 07 Oct 2010 at 8:53am
IP IP Logged
Printable version Printable version

Forum Jump 		You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum

HOME | FREE EBOOK | PROGRAMMING GUIDE | PURCHASE | REVIEWS | CONTACT ME | FAQ | LINKS | PRIVACY | CLICK PLAYS | KONACAD

© 2004-2026 Brian Bischof. All Rights Reserved.