If it is possible of course, but in most cases, it is.  Why it is taking so long, probably, is that the for every item in the main report, the subreport is being called.  If you have 100 items, that is 101 calls to the database.  If the network is busy, slow, or there is a lot of data to filter through, all of this can slow the report, and then it needs to format the data.  If you can cut the data to 1 call to the database...well speed will increase.  Also you can time your sql execution, maybe it is taking a long time and some optimization can be done...it may not all be Crystal's fault.

 

The simplest way, which may make for a long datarow is to create a super record that has the main and the subreport data contained in it.  Then the main report data is displayed as a group header and the subreport data is displayed as details. this would be done in a stored procedure, more likely than not.  Binding to the tables directly, may not allow the data to be properly created (this might be where the unrelated data would make sense, too many or too few records)

 

This gives 1 call to the database, instead of the number of the rows in the main report +1.