Backward Compability

Posted by: stefanmaehr on 4 August 2017, 3:01 pm EST

  • Posted 4 August 2017, 3:01 pm EST

    Hello NG,

    I got a big problem when using AR1 and AR2 on the same machine (again).
    We redistribute a newer Application using AR2, we included as posted here in the forum both the actrpt.dll AND actrpt2.dll in the setup project and redistribute both in the System32 folder of the target machine.

    When there is another product installed using AR1 the newer Solution using AR2 breaks when hitting the print button (print preview works). When I deregister AR1, the reregister AR1 and then register AR2, AR2 works fine BUT the other Application using AR1 is not working any longer (No data in Preview ...).

    We've already tried several approches to solve the problem (e.g using .local files ..).

    I mean, what the heck, Is a largerly known company like DataDynamics not able to programm backwardcompatible COM-Components??
    Do you do any testing with your products??

    ANY IDEAS OR SOLUTIONS ??

    Thanks in advance for all your help.

    Stefan
  • Replied 4 August 2017, 3:01 pm EST



    Hello,



    What if you just put the DLL's in the local bin folder for that application and
    did not register them.  I think the problem you are running into is more
    related to 'DLL HELL' then ActiveReports.  If you keep the DLL's in the
    local bin folder for the application you should not need to register them and
    the VB6 application will look first into the bin folder for the appropriate DLL.

  • Replied 4 August 2017, 3:01 pm EST

    Thanks for the suggestion, we already tried this (using a Exename.exe.local File + moving the AR2 Report dll to the Application Folder), unfortunately no success, if  I do it like that, even the AR Print Preview refuses to open.

    With best regards

    Stefan
Need extra support?

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

Learn More

Forum Channels