Errors Upgrading from AR6 to AR13

Posted by: kamau on 30 January 2019, 1:58 am EST

    • Post Options:
    • Link

    Posted 30 January 2019, 1:58 am EST

    Yes, you read that right, I’m upgrading from ActiveReports 6 to v13. Have an old class library wrapper and win32 application that was written in 2007, and over the years over 400 reports have been created using it. Well, upgrade time has arrived.

    I installed v13, and slowly started replacing all the references, and while all the errors have been eliminated, the library still won’t build, I had to enable “Diagnostic” output in VS2017 to even see the errors. The errors are:

    error BC30002: Type ‘GrapeCity.ActiveReports.SectionReport’ is not defined.

    error BC30002: Type ‘SectionReport’ is not defined.

    Intellisense is working and the above Types are detected ok, it just won’t build. Tried the usual tips of removing all references, adding them again. Nothing. Also noted that the licenses.licx file was not being created, added a temporary ARReport to the library as the help suggests, nothing, no licx created. Tried pasting the suggested text for the licx file, no joy, error changes to



    Unable to resolve type ‘GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports’

    What could be the issue?

    Also note that I’m working with a trial license as I’ve not yet gotten approval to purchase the license.

    Environment:

    Win 10 x64

    VS 2017

    AR13 installed but on Trial License

  • Posted 30 January 2019, 6:30 am EST

    Hello Kamau,

    Thanks for showing the interest in the AR13.

    There are drastic changes from AR6 to AR13. The namespaces or object model is very different in AR13 as compared to AR6.

    First of all, AR13 supports only 4.6.2 or higher .Net FW. Please change the FW of all your application to 4.6.2 or higher.

    Also, we don’t have documentation related to the API changes between AR6 And AR13. However, we have the documentation related to the API changes between AR6 =>AR12 and AR12=>13.

    Please refer to the following link: https://help.grapecity.com/activereports/webhelp/AR13/webframe.html#BreakingChanges.html

    Could you please go through the above link. If the problem still occurs, please send one of your projects so that I will try to replicate the error at my end and provide you the solution accordingly.

    Thanks.

  • Posted 30 January 2019, 8:39 am EST

    Upgrading to .net 4.7, resolved the build issues, designer is now running as expected. Amazing that 12 year old code from 7 versions behind still works.

    Interestingly the old viewer still renders the report even if it’s from the new designer, only that now I need a license for the designer after 30 days.

    Is this expected behaviour? I would have figured it would have refused to render. Does this mean we can keep using the old viewer from v6?

  • Posted 30 January 2019, 9:32 am EST

    Hello,

    Actually, the report structure of section report is the same between AR6 and AR13. I am assuming that you are using the “.RPX” format file. If my assumption is correct then you can use the AR6 or AR13 viewer to preview the report. However, when if you use the new feature in section report which is implements after AR6 then report can only preview in AR13 Viewer only.

    Also, AR6 never supports Win10 and VS2017.

    Hope it clarifies.

    Please revert if you have any questions. I am more than happy to help you.

    Thanks.

  • Posted 30 January 2019, 9:39 am EST

    Thanks for the clarification. Obviously after 12 years, there no discounted “upgrade” option for legacy licensees? Sorry, have to ask :frowning:

  • Posted 30 January 2019, 9:47 am EST

    Hello Kamau,

    Regarding sales related query, I would recommend you to contact our sales team directly at “us.sales@grapecity.com” or 18008582739(9AM - 5PM EST).

    Thanks.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels