>>If that's the general direction you'd like to go, I can post some samples.
>
>That would be great! Thank you Kevin. Is there another/better approach?

Depends on the situation. Last time I used it for something major, it was for an insurance company that generated different policy documents at the end of the day. So on any given day, there might be 100 new endorsements and 200 renewals, where reports A, B, and C were generated as PDFs and transmitted to a mail room software app.

So the reports were developed against SQL Server stored procedures, and then called from a .NET app that invoked a class library I wrote that abstracted out the Crystal API.

It was a windows app, but had very little in the way of a UI and could have been a web app or even a service.

Like I said, I haven't worked in the Crystal area in years, but this was a fairly common approach for this type of situation. So if your situation is anything like what I just described, let me know and I can post some samples.