Interesting thoughts.

Thanks Kevin.

>Is there anything that Crystal does that isn't possible in SSRS 2008 ?
>
>There are certain grouping functions in Crystal that either don't exist in SSRS 2008, or at least require some significant modifications.
>
>Crystal's runtime formula language is a little richer than what SSRS provides - which sometimes means you might have to generate more metadata in your result set if you're using SSRS.
>
>Charting in SSRS 2008 is much better than 2005, but CR still has a few more charting capabilities.
>
>The CR report preview window is, IMO, a bit more programmable, though for some projects that might not mean anything.
>
>If Tracy Holzer is reading, I seem to recall something she was working on a few years ago, where she was prototyping in both CR and SSRS....my memory is hazy, but it had something to do with exporting specific content. Maybe she remembers what I'm referring to.
>
>Of course, depending on what types of reports you currently have, these could be small or non-issues, or they could be significant ones that would take weeks or even longer in developer time to come up with workarounds. If you have a large # of reports in CR, odds are decent that you're talking about a non-trivial development effort. There are different migration tools and services out there, though I haven't used them.
>
>This link is a bit dated, but still a good reference, for migrating from CR to SSRS
>http://technet.microsoft.com/en-us/library/aa964127(SQL.90).aspx
>
>
>If I were staring a desktop-based reporting solution today and could pick the tool, I'd probably still lean towards CR. If it were a browser-based solution, I'd definitely go with SSRS. SSRS also has server-based features to create report subscriptions (e.g. to email reports or export to PDF to specific recipients on a schedule, and generate a history log of the output). With SSRS you get closer integration to SQL Server and SharePoint (the latter won't be relevant if you're not using SharePoint).