One thing to remember, as well, is that Crystal is read-only against your database. So it's not going to damage data. (Well, if you base your report on a stored procedure, that procedure can update or change data, but Crystal itself doesn't modify your data). So the worst you can do is create a join that just returns too many records and serverly slows down your server, which can make a lot of your fellow workers very unhappy (assuming you're running on a server like Oracle or SQL Server). Which is why I would strongly echo Synapse's statement that you need to understand your database. Cartesian products are rarely your friend.