I am with a Sage partner and have been getting A LOT of calls about "broken" custom Crystal Reports after upgrading, and I'm finding nothing wrong in the reports themselves.  It doesn't seem to be specific to version 16 or 17, and there aren't really and "common" issues/errors - but there's enough of them that I'm getting highly suspicious that something Sage did in the year-end update is "breaking" Custom Crystal reports.

The problems run the gamut:  One can "preview" a report and print/save from the CR runtime preview, but can't print or send to file from the regular print window; Another couple the report runs fine when opened and previewed in Crystal Designer and when run from a Reports menu link, but when set as a default report on their desktop it does not work (one customer gets an "object reference error", the other it will freeze when one of the jobs is selected in the drill-down menu).  Another one, the report runs fine on my test system, but not on his.

It's not unusual for me to run into one or maybe two of these each year, but this year it's been very out of the ordinary for the number of problems I've had with Custom Crystal Reports.

Anyone else having the same - and been able to fix their problem?  I'm open to any and all suggestions at this point, because both me and my clients are getting very frustrated right now.