going back to AR11 from AR16

Posted by: darin on 11 July 2022, 2:44 am EST

  • Posted 11 July 2022, 2:44 am EST

    We had to go back to AR11 from AR16 due to the slow printing that is a known issue in AR16.

    Steps I did:
    1. Removed AR16 from Control Panel/Programs
    2. Changed my solution to reference the AR11 DLL and not the AR16 DLL.
    3. Went from .NET 4.8 to .NET 4.6.2 (since AR11 works up to 4.8)

    Two issues we have discovered so far.
    1. Some images saved when running on AR16 do not pull up correctly when on AR11 (some are fine, some are missing lines). We read the saved RDF from a SQL table and display it.
    2. The reports run fine (and fast to a printer), but we can't save it to an XLS on some systems.
    Dim xls As New GrapeCity.ActiveReports.Export.Excel.Section.XlsExport
    xls.FileFormat = GrapeCity.ActiveReports.Export.Excel.Section.FileFormat.Xlsx
    xls.Export(in_myDoc, in_file)
    xls.Dispose()

    the line that is crashing the system is the xls.Export(in_myDoc, in_file).
    the event viewer is showing it is an appcrash (this is .NET4.8, but same occurs for all .NET):
    Faulting application name: Menu.exe, version: 4.2207.8.11, time stamp: 0x62cc4368
    Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624cf48c
    Exception code: 0xc00000fd
    Fault offset: 0x0004d4f6
    Faulting process id: 0x1b88
    Faulting application start time: 0x01d8953ca7899396
    Faulting application path: C:\pgm\Menu.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    Report Id: 0456d867-15e5-4372-a8f1-beddfc1a6390
    Faulting package full name:
    Faulting package-relative application ID:
  • Replied 11 July 2022, 10:21 am EST

    I got the save to XLS fixed (had to go back to .NET 4.5 and make sure all the AR16 packages were removed).
    The reading of an AR16 saved report is still having random issues on AR11.
  • Replied 12 July 2022, 3:15 am EST

    What can I do to get RDF files created in AR16 to be readable in AR11? There has to be a way. We have multiple customers that tried to use AR16 for anywhere from one week to a month and we had to roll them back - now most of their saved RDF's either do not display (unknown canvas item with unknown length error) or they display incompletely (missing logos and other fields).
  • Replied 12 July 2022, 4:10 am EST

    Hi Darin,

    Happy to know that you were able to fix one of the issue by yourself and thanks for sharing the solution with us it will help others having similar issues.

    >> Some images saved when running on AR16 do not pull up correctly when on AR11 (some are fine, some are missing lines). We read the saved RDF from a SQL table and display it.
    The images saved from newer versions of ActiveReports are not correctly rendered in older versions in a know issue the suggested solution for this is to open the reports in a ActiveReports 11 designer and re-add the images.
  • Replied 12 July 2022, 4:26 am EST

    The issue isn't in the designer. The RDF file was printed from AR16 and we are now trying to read the RDF file to display it in AR11.

    See attached.sample-invoices.zip
  • Marked as Answer

    Replied 14 July 2022, 1:18 am EST

    Hello Darin,

    Apologies for the delay. The sample RDF files you shared(AR11-invoice, AR16-invoice) seems to be identical. It seems that both of the files are saved using ActiveReports 16. Regardless, ActiveReports 11 is a legacy product and the encoding for RDF file has been modified with later versions of ActiveReports also. The suggested solution for this would be to re-print the reports using ActiveReports 11.

    Also, we have released a hotfix for the printing issue. The printing performance should be much better than before. Although I wouldn't expect it to be similar to the printing speed of really older versions of ActiveReports.

    You can download the hotfix using the following link:
    https://cdn.grapecity.com/ActiveReports/ar16/ActiveReports-v16.1.3.msi
  • Replied 14 July 2022, 1:20 am EST

    Yes, the RDF was created with AR16, the attachment was just showing you what that RDF looked like when opened in AR11 compared with AR16.

    We will download the hot-fix and see what the speed is. Thank you for the update.
  • Replied 18 July 2022, 1:15 am EST

    The AR16 update does seem the speed is almost back to AR11 speed. We are still doing a lot of tests.

    Thank you for your help.
  • Replied 16 August 2022, 6:44 am EST

    The 16.1.3 hot fix does not seem to be part of a release that is on the web site for download.
    When is the release that has this hot-fix going to be released? Or, is it ok to use hot-fix 16.1.3 as the version of AR16 that we release to customers?
Need extra support?

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

Learn More

Forum Channels