You still can’t see CR 2011, but if you want to know what some of the problems are you can read the release notes.
Nothing earth-shattering, but a few of interest:
ADAPT01353630 – you can’t save a report with a formula error. You have to fix the formula or the report won’t save.
ADAPT01338584 – there are a few problems exporting to PDF if you use ‘justified” alignment.
ADAPT01323911 – Stored procedures can no longer be used with SQL Server wire protocols (Native or Classic).
And, the one that surprised me the most was ADAPT01358869 which says “If you map a “Timestamp” field from an SQL Server to Crystal Reports, the correct data is not retrieved and a blank image appears”.
I first read this to mean that CR wouldn’t read a date-time value. But I learned that SQL Server has a specific data type called ‘Timestamp’ that is used by SQL server for tracking changes and facilitating recovery operations. It has nothing to do with a DateTime fields that store the date and time a record was created or updated, which I would call a TimeStamp.
Many of the other issues are related to the server-level environment, but if you see anything interesting that I missed, drop me a line or post a comment.