I just tried using two Commands against the same database, and got really weird results. First, I should explain that the use of two separate commands was required since one table I was pulling data from needed to be UNIONed to a second table, but I needed data from a third table to display a comparison between it and the first two.

I put 2 crosstabs in : one showing a summary on the first two tables, the other showing a summary on the third. When the data started coming in, it grew quickly to over 10 million records read. I stopped it before it finished, but obviously something was wrong since there isn't anywhere near 10 million records between the three. If I take one of the crosstabs out, it appears to work fine. Any ideas on what would cause this behavior? If any additional info is needed, let me know.

I pretty much stripped the commands to the bare basics. Started a new report, added 2 commands that pulled one field with one WHERE clause from different tables. Then added two crosstabs in to show the summary for each command. In fact, the run that produced over 10 mil. results was after I had done that. The original commands produced a lot fewer, but still a considerable amount above what it should have been. It should also be noted that the result count for both commands, according to summaries, were equal.

Yes, a stored procedure would be optimal. Unfortunately, due to the sensitivity of the data (police database), modifying the database itself isn't acceptable.