easiest way is: Put the class definition for "clsErrorLog" into the script part of the report.
Is the DLL really imported?
PML or CMDLINE:
import /PATH\file.dll
handle(1000,0)
endhandle
easiest way is: Put the class definition for "clsErrorLog" into the script part of the report.
Is the DLL really imported?
PML or CMDLINE:
import /PATH\file.dll
handle(1000,0)
endhandle
Cheers
Hi aequitas,
Good day!
I'm doing it in the Report Designer Script using C#. There's no problem in importing DLL using PML.