Crystal with SQL Server stored proc

I'm somewhat new to Crystal and I'm writing reports based on stored procedures which is not the norm here so when I run into problems, I hear "I've never written a Crystal report from a stored procedure." I have 2 questions:
1) Does anybody routinely do this?
2) I wrote a rather complex stored procedure, created a report and it was working and published on Lawson's dashboard for testing. I changed something and changed the proc name (I don't remember why) and the report will not work now. And I have renamed the proc, created a new report based on the proc and it still won't work. Does anyone have any ideas on what could be the issue. The users that tested it want it bad and I am stuck. Any thoughts/suggestions would be greatly appreciated.

I personally never enjoyed having to work with Crystal Reports so wouldn't be in a position to advise as to how to get this to work, however, if you are running the latest version of SQL Server (2008) you could explore utilizing the BI Reporting Services feature that come with 2008.

Sorry I couldn't help with Crystal I would create a custom report with code before using that solution when it was possible in my developing days.

Hope this helps

Larry Darrah

Although I work for MS as an Architect Evangelist my opinions and occasional errors are my own and are not to be misconstrued as Microsoft's

Yes, I first wrote it in SSRS--so prefer that, but no one here knows how to deploy it securely. So I rewrote it in Crystal. I had it working but it quit working last week and I started uninstalling IE service packs and was going to go back to IE6. Before I got IE7 uninstalled, I found out it was a Lawson dashboard implementation that was making the report not work for users. However, I cannot change it now--it's like Crystal isn't talking to SQL Server, even if I create a new report. So I'm going to get the service packs reinstalled and see if things work then. I much prefer SSRS.