Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Crystal Reports 2008 Excel Export Compatibility Patch - second attempt :)

Hello, I actually have a question related to the following thread, so I posted there and was recommended to start a new thread:

Crystal Reports 2008 Excel Export Compatibility Patch?

Question is related to the following doc, specifically, is this patch still available for CR 2008 or not?:

A response from Don suggested this wasnt available for CR 2008 although this is confusing since the doc refers to CR 2008. My response was as follows and is essentially the question I still have (more so because we have another PeopleSoft/Oracle customer whos come across this doc and wants to know how to apply the fix for CR 2008). Thanks very much in advance!


Hi Don, I know this is an old thread, but Im also running into the same issue and am confused by your statement since the referenced PDF doc says this patch is available for CR 2008. Did you mean that the patch is no longer available or supported for CR 2008 for some reason? If so, any idea why?

Im a developer for Oracle/PeopleSoft and our PeopleSoft suite includes OEM Crystal. We recently upgraded to CR 2008 for our latest release and we are getting the same complaint from a few customers about not being able to output the XLS in Excel 8.0 compatiibility mode like before (In Crystal 9, we used the \Export\Excel\CompatVersion=80 registry key to enable this). So if this patch is available, it would be a huge benefit for us to be able to point our customers to it. If not, please still let me know eitherway.

Thanks very much!


Former Member

Hi Andrew,

So the story is the Rubik's patch has been available from CR 9 up until CR XI R1 as a simple download. In R2 and above to get it you have to log a case, work with a Report Rep to try to design your reports so they use the new export dll. To get you by until you have time to do so, and after filling out a query for the PM to get info on how to possibly improve the updated export dll to meet your needs, he will then send you the patch on the agreement that this is the LAST time you ask for it.

Support no longer has access to the patch so all requests must go through the Program Manager who keeps tract of who received it.

Bottom line is you need to update the reports to use the new export model.

That old legacy dll was bugging and impossible to maintain.

You can [purchase a support case here|].

This is not a bug and has been this way for 10 years now, time to update your export model and Excel Macro's....

Thank you for your understanding


0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question