Chris - I feel your pain.
Here is a link for you. I am NOT spamming for this guy. He has helped me a lot and some of the stuff (under /bookmarks.html) is free. Check it out. He has a periodic newsletter as well.
We use CR 10 with SQL 2005. Most of our reports use SQL procs. Some use tables with data generated in a prev SSIS pkg. And many use parms that actually reside in the SQL procs.
I did write a VB.Net console application (which accepts report params) that is executed via Windows Scheduled Tasks (creates Crystal report, emails it) with a report id tied to a SQL table, and a param. Example : exec c:\Crystal\CrystalConsole.exe "22" "JDOE"
The SQL table includes fields like: report_id (22 in this case), crystal report file name (xxxxxxxx.rpt), report file path (where is it located?), server name, db name, username, pw, email addresses (mail_to, mail_cc, mail_bcc), export file type (PDF), smtp server name, email subject text, email body text, etc.
This setup works quite well for scheduling/running reports at night.
I wish you the best. Crystal is the reason I'm bald now!:doze: