What is the most flexible method to use in creating CR reports for an n-tier application?

Currently, I'm using parameterized queries created in Crystal SQL Designer as datasource for my CR reports but I'm wondering how the reports should be properly deployed when I'm ready to deploy my applications.

Since my app is n-tier, the client app doesn't use any ADO-recordset directly but bind to objects in separate business-DLL that in turn uses recordsets received from server-based data-DLL. Using this approach, the client computers doesn't require a direct connection to the DB.

However, because of CR, now I must have DSN (or at least maintain login access if I choose DSN-less connection) which add more complication, just to print reports.

Lastly, MS did a decent job putting out a sample Windows DNA application for developers like myself to learn and apply techniques but nowhere do they address the preferred method of setting up reporting.