Bertrum:
Of course one can use subreports, but they are not a particularly good solution in many instances. And looking at src2's situation, I doubt if subreports are a good fit. I'm quite familiar with databases where current transactions and historical transactions are in separate tables/databases, and often one wishes to combine the data and do things like group it by vendor and, perhaps, sort by order amount or product rather than order date (which is generally the driving factor on active and historical tables. In other words, the original location of the record has no bearing on how you want to display it in the report, and, in fact, gets in the way). And in the situation where you use subreports, doing totals across the subreports and main report is far more cumbersome than simply getting your data together outside of Crystal and then passing Crystal a single dataset.
So I would echo synapse's comments. I think in terms of a general approach, it is far better to depend on your database to collect the recordset for Crystal than to have Crystal itself try to do a lot of heavy lifting.
If Lotus Notes itself doesn't allow for a view across databases that would bring the two tables together (it's been a long time since I've worked with Notes so I can't say), and if src2 doesn't have access to something like ReplicAction which would be able to pump the two views into a single table in SQL or Access, then using Crystal as the query engine may be the only choice. But it should be the last choice.
