>PMFJI. But if you were to do now (today) the same thing as you did for an insurance company using Crystal, would you have chosen a different approach? That is, would you have gone with Crystal still now?

OK, that's two separate questions :)

They had over 100 reports in Crystal, and it was an internal application, one of many that either used WinForms or WPF. The application is still running today, even though I developed it years ago (obviously, it's been enhanced many times). At the time, Reporting Services wasn't a great option (this was before SSRS 2008 came out, which was the first truly STRONG version of SSRS)

SSRS has a data-driven subscription capability in the enterprise edition of SQL Server , whereas with Crystal you had to write more code. Then again, writing more code gives you greater control. My biggest reason for leaving the Crystal world and moving to SSRS was Crystal's approach to licensing once you went outside Winform apps. The market apparently felt the same way, as Crystal lost market share and SSRS gained.

It's hard to answer that question - but if the client today needed to do what they needed years ago (which, they still do) , and if they still used Crystal (which they still do), I can't honestly say I would have approached it much differently.