Fascinating. I really didn't know VB had that functionality. Learn something new every day, I suppose.
I just want to be sure that we're on the same page here: are you trying to force Crystal to sleep because you're assuming it will return the sections prior to the sleep, before then returning the other sections?
The only way this can happen is if the section before the sleep is revealed in a subreport, with everything after the sleep in the main report or another subreport.
If you do something to force Crystal to waste time without incorporating an initial subreport, you won't see any data returned at all before the sleep - unless you force the time-wasting to ensue after the first page of the report. All you'll get is a blank screen with "Reading Records..." in the corner.
The initial loop suggestion would be aimed at creating a loop which was set to loop, say, 1000 times. For loops/Do While loops are as they are for Basic - check out F1 in Crystal.
You could also call a subreport, which depending on what the subreport was doing, would certainly take a second or more to execute. (You'd have to ensure that if it was placed in a recurring section, that the section would be set to suppress on each subsequent run after the initial time.)
I've never heard of anyone wanting to make their report slower before, but there's certainly a few ways to harm the performance. I'm just not sure that the way the performance will be hindered, and what you expect are the same.
Naith
