"Agnes" <agnes@dynamictech.com.hk> wrote in news:#JefQK5BHHA.3620
@TK2MSFTNGP02.phx.gbl:

This is due to the fact the UI thread (main thread) is tied up generating
the report.

You can try running the the report on a separate thread - but CR is COM
based... so I never had too much success doing it that way.

Another possiblity is to use CR.NET's "Push" model.

The Push model uses a ADO.NET dataset to pass data to CR. Rather than
connecting directly to the database, you fill a dataset and pass it to CR.
Fill the dataset on a separate thread and this will prevent the GUI from
lock up during report generation. Once the dataset is filled, you assign it
to the Report's DataSource property. Thus, the report will only be locked
up for a split second for layout - rather than for the long query time.

Hope that helps.