Sharing a custom report

Peggy Dixon

I need help sharing a custom report with a friend at another institution. Would they have to re-create the whole thing within their own database? I'm sure someone out there has shared reports. Appreciate any advice. 

Alan French

If you're sending them the .rpt file, I wouldn't have thought there'd be any difference between them setting up a new custom report using that compared to doing it with one they'd built from scratch.


They will need to recreate the export with all the same fields that you have in yours, otherwise when they go the run it Crystal will probably pitch a fit about the structure of the database having changed, if it can't find all the fields/tables it's expecting.

James Andrews

Alan French:

If you're sending them the .rpt file, I wouldn't have thought there'd be any difference between them setting up a new custom report using that compared to doing it with one they'd built from scratch.


They will need to recreate the export with all the same fields that you have in yours, otherwise when they go the run it Crystal will probably pitch a fit about the structure of the database having changed, if it can't find all the fields/tables it's expecting.

They'll also need to set the database location in crystal. CR loses its mind if it can't find the data source.

Peggy Dixon

After thinking about it, I came to the same conclusion. Thanks, Alan and James. Hopefully CR will cooperate with me

Rachel Slager 2

As stated, they do need to update the database file location in the .rpt file, and they need to create their own export.  Help them out by going to your export.  First, take a screenshot of your output.  Second go to File, then Preview Export File Layout.  Remove your data, keep the RE headers.    Why both?  Because not all export fields in the screenshot will clearly indicate which category they originated from whereas those super tech headers do - especially important if any data pulls from things like Relationships.