Skip to Content

Migrating reports generated with Crystal Reports XI SP6 to Crystal Reports 2016 or 2020

Could someone please explain if there is a migration path from legacy .RPT file generated using CR XI R2 to one of the newest versions either 2016 or 2020?

I need to gaige the complexity of transitioning, and if SAP Crystal provides a migration tool available in order to help facilitate the process.

Or worst case, would it be a total rewrite of the the reports (.RPT) and SDK handling the reports.

Add a comment
10|10000 characters needed characters exceeded

  • Hi Jamy,

    Thank you for visiting SAP Community to get answers to your questions. I am here to help you to get the most out of it.

    First of all, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers (if you haven't done so already), as it provides tips for preparing questions that draw responses from our members.
    For example you:
    - can outline what steps you took to find answers (and why they weren't helpful)
    - can share screenshots of what you've seen/done
    - can use a descriptive subject line

    Please also make sure you're using all appropriate tags, so the right experts can find your question. Overall, the more details you provide, the more likely it is that members will be able to assist you. Should you wish, you can revise your question by selecting Actions, then Edit (although once someone answers your question, you'll lose the ability to edit the question - but if that happens, you can leave more details in a comment).

    Finally, if you're hoping to connect with readers, please consider adding a picture to your profile. Here's how you do it: https://www.youtube.com/watch?v=F5JdUbyjfMA&list=PLpQebylHrdh5s3gwy-h6RtymfDpoz3vDS. By personalizing your profile with a photo of you, you encourage readers to respond.

    Best,
    Lena (SAP Community Moderator)

Related questions

1 Answer

  • Posted on Sep 03 at 03:31 PM

    Hi Jamy,

    First question is what SDK did you using in CR XI?

    For the version of the report it should not have any issues.

    Mostly the DB Client could cause some issues, changes in their Clients may have introduced SQL issues but mostly the reports should be fine.

    If your app is written in .NET then get CR for VS SP 28 from here:

    https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

    Read all of the info about SP 21, important updates required etc.

    Note: Cr for VS is the only source for .NET now, we no longer install with Visual Studio nor is it shipped with CR Designer.

    PS - if you are upgrading from the legacy RDC engine there is no migration path for that, it will be a complete rewrite of the CR parts in your app. Samples on the WIKI page for Parameters and Printing.

    Don

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Don,

      Our reports are produced from within a legacy VB6 application. The custom component responsible for report handling references the following libraries.

      And this is the components

      The reports are generated and edited using the following designer product.

      This is the programming library being used

      Have I provided you enough information for you to understand our environment?

      If not please let me know what else I can gather.

      I have spent 2 days going thru the community posts trying to find an answer to a problem which many posts have been written on and you have responded to. We are one of the unfortunate companies who are now faced with the trials and tribulations of customers requiring tighter security, sending us down the path searching for a data provider that supports our TLS needs. Having a legacy app dependent on SQLOLEDB like others we replaced it with MSOLEDBSQL. After running a couple of reports we ran into a issue mentioned in another post where it was thought that CR generated invalid SQL statements while Converting DateTime values using our version of CR XI R2 in combination with MSOLEDBSQL. That is where we are stuck at right now.

      During my search in this Community site I came across links to a patch that claimed it would resolve the issue, but following the link resulted in a not found page. Not sure if it was false information or not. I may be able to dig it up if you have an interest.

      I have followed your posts and you seem to be very knowledgeable on the subject I am speaking about. So I would like to ask, Is our ONLY option to upgrade? Are there only certain known errors while using the new provider and is it possible there are workarounds that could be made by changing the report or stored procedure design?

      If the answer is still no, would SAP provide any paid consultation/instructional services to so as to expedite the migration/upgrade process?

      Any and all help you can provide us with is honestly appreciated. Thanks Don.

      hsyhh.png (31.3 kB)
      zv7gz.png (18.0 kB)
      uor6j.png (70.3 kB)
      negsc.png (43.6 kB)

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.