Error loading Report in DLL - Invalid Pointer Operation
Good Day,
I have recently ported our application from XE5 to RIO. Our application is split into various DLLs. All reports are in separate DLLs.
The DLL is loaded with LoadLibrary and Freelibrary.
My problem is when the library is loaded for a second time (Load and Free the first time), I get a runtime RTL Invalid Pointer Operation error.
I have create a test app that calls a test DLL. The only units included in the uses clause is report builder units. On the second iteration the app completely crashes when I do LoadLibrary.
I am unable to debug further to see what the problem is.
Has anyone experienced something similary?
I have recently ported our application from XE5 to RIO. Our application is split into various DLLs. All reports are in separate DLLs.
The DLL is loaded with LoadLibrary and Freelibrary.
My problem is when the library is loaded for a second time (Load and Free the first time), I get a runtime RTL Invalid Pointer Operation error.
I have create a test app that calls a test DLL. The only units included in the uses clause is report builder units. On the second iteration the app completely crashes when I do LoadLibrary.
I am unable to debug further to see what the problem is.
Has anyone experienced something similary?
Comments
I tested the RB DLL demo and did not encounter any issues. The demo is installed to
c:\Users\Public\Documents\RBuilder\Delphi x\Demos\DLL
There is a CallDLL project and a FormDLL project. Have a look at the source code and comments.
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Thank you for the reply. I have revisited your demo in the directory and all is good until i start adding my runtime packages.
I add the following as part of my list:
rbIDE2026;rbDB2026;rbCIDE2026;dclRBADO2026;rbRAP2026;dclRBFireDAC2026;rbDIDE2026;rbUSER2026;rbDAD2026;dclRBDBE2026;rbUSERDesign2026;rbADO2026;rbRIDE2026;rbFireDAC2026;dclRBE2026;rbRCL2026;rbDBE2026
I add this to the CallDll and RptDll.
It seems OK when I only have it in the RPTdll, but as soon as I have it in both it becomes a problem.
Regards,