run time

[happydermis]

I have a report with a run time of about 50 minutes. Does this sound normal??____I can hardly debug the report since I must wait those 50 minutes until I can see if I did right or wrong with the report____Thanks, Dekers

[kfleming]

The complexity of the report, the size of the data files and the speed of the I/O will be the main factors that determine the time that it takes for a report to execute.____Kathleen__R&R Support

[happydermis]

This is why I tried to keep my report as simple as possible and to use the minimum I need. Is it normal for reports to take such a long time or does my report need extremly long time to run?____

[castrass]

Keep in mind that reports with lots of total fields and summary bands will take longer in general as well. You don^t mention if it^s an Xbase or a SQL report. If Xbase, limit the scope to just a subset of the records in the master table. For SQL, limit it to the first N records.

[happydermis]

thanks castrass,____I use the Xbase version (unfortunately...). The problem is: I don^t think it is possible to limit the scope of my report since I am using a multiple scan report. In this kind of report a ^pseudo^ table is used as the "main" linking table to two or more tables all in one scanning level. The scope of the pseudo table is being limited to 1 but as far as I know there is no way to limit the scan of tables on other levels.____Do you know anything about it? ____Thanks, Dekers____P.S - at this time I am looking at about 50 minutes per report, which is actually unuseable __