Skip to main content

Crystal Reports Version History

Crystal Reports has been around for a long time. Some might say too long. Over its 19 year history its certainly become very widespread, and I have nothing bad to say about its presentation. But 19 years of evolution and attempts at backwards compatibility can play havoc with an object model. A case in point: If you want to attach a reports to a different database at run time - a pretty common occurrence - you have to write surprisingly unlikely code. Its easy enough once you know how to do it, but why isn't there any centralised connection information?

Crystal Reports has also changed hands a lot over the years, from being owned by Crystal Services, then Seagate, then Crystal Decisions, then Symantec, then Business Objects and finally SAP. This led to a plethora of different version names, and to make things more complicated, the versions that were bundled with Visual Studio were separate releases in themselves.

I haven't found any good summaries of the versions and their compatibility with Visual Studio, so here's an attempt to do that:

Official NameVersion NoNotes
Crystal Reports for Visual Studio 2010 13 ? Not bundled with VS 2010, has to be downloaded separately
Crystal Reports 2008 Service Pack 0 SP0 made Crystal Reports 2008 compatible with VS2008
Crystal Reports 2008 This was not compatible with VS2008 initially. Service Pack 0 fixed that.
Crystal Reports XI Release 2 11.5 
Crystal Reports XI 11.0 
Crystal Reports Basic for Visual Studio 2008 10.5.3700.0 This came bundled with VS2008. Not to be confused with 'Crystal Reports 2008' which is V12, above
Crystal Reports for Visual Studio 2005 10.2.3600.0 This came bundled with VS2005
Crystal Reports 10 10.0.3300.0 
Crystal Reports 9 9.2.3300 
Crystal Reports for Visual Studio .NET 2003 9.1.5000 This came bundled with VS2003
Crystal Reports for Visual Studio .NET 2002 9.1.3300 This came bundled with VS2002
Crystal Reports 8.5  
Seagate Crystal Reports 8  
Crystal Reports 7  
Crystal Reports 6  
Crystal Reports 5  
Crystal Reports This came bundled with Visual Studio 6



Popular posts from this blog

Copying data to Salesforce Sandboxes using TalenD

A common problem with Salesforce Developer Sandboxes is that they are blank. Really you're going to want some data in there, so there are various strategies for copying data from your live instance to the Sandbox. There are some paid-for solutions - SFXOrgData , Salesforce Partial Data Sandboxes - but if you've got a decent ETL tool you can build your own. There are a bunch of free ETL tools for Salesforce: JitterBit Data Loader is good for quick ad-hoc tasks but the free version makes it difficult to manage specific ETL projects or share projects with other users Pentaho Community Edition - an open source edition of the enterprise version Apatar was a free open source Salesforce ETL which still works but development seems to have stopped since 2011 TalenD Open Studio is an open source ETL tool For the task of copying data from live to a Sandbox, either Pentaho or TalenD Open Studio could be used, depending on preference. Here's a good comparison of the dif

SSRS multi-value parameters with less fail

SSRS supports multi-value parameters, which is nice, but there are a few issues with them. This is how I deal with them. Two of the problems with SSRS multi-value parameters are: You have to jump through a few hoops to get them to work with stored procedures The (Select All) option, as shown above The reason the (Select All) option is a problem is that it is a really inelegant way of saying 'this parameter does not matter to me'. If you have a list with hundreds of values, passing all of them as a default option just seems wrong. Also, if your report shows the user which items they selected, printing the whole list when they choose (Select All) is excessive. So in this post I'm going to show my particular way of: Jumping through the hoops to get Multi-Value params in a stored procedure Adding a single '--All--' value that the report interprets as meaning all the options. Getting Multi-Value params to work with Stored Procedures This is

Remote Desktop on High DPI screens

Scott Hanselman wrote a nice blog post back in January about some of the issues you might face running Windows on a High DPI screen like that of a Surface Pro or Lenova Yoga. I'm kindof mystified that he didn't mention Remote Desktop though because thats been the number one problem for me on High DPI screens. That said, if you remote into very recent Server OS's like Windows Server 2012 R2, then apparently Remote Desktop will sort out the DPI scaling automatically. Perhaps Scott hadn't noticed the Remote Desktop issue because he only remotes into Server 2012 R2. Certainly if I was Scott, I wouldn't remote into anything less than that. But, in practice, I regularly have to remote into Server 2008 machines and yes even Server 2003. If you do that from a high DPI screen, the remote desktop is rendered at regular pixel size, which makes everything tiny. Its hard to show screenshots of High DPI screens that correctly convey the pixel size, so I've photoshoppe