cascade of reports ( one calling another with pl/sql transaction stored procedure in the calling cha
Hello to everybody,
Is there any problem when calling PL/SQL stored procedure with transactions ( insert, update ) in Reports trigger ( runrep 6i, 10g ).
The transaction supoose to be commited right after the call in reports or is it better to call in pl/sql.
Is there a possibility to preserve uncommited status of the transaction during second report call with srw.run_report ( or migrated version with hyper link )?
So the first control of input data is reported with the button/hyperlink for launching pl/sql procedure with transactions.
After the pl/sql stored procedure call the second output control report is launched to display the result of PL/SQL stored procedure.
Is there any problem when calling PL/SQL stored procedure with transactions ( insert, update ) in Reports trigger ( runrep 6i, 10g ).
The transaction supoose to be commited right after the call in reports or is it better to call in pl/sql.
Is there a possibility to preserve uncommited status of the transaction during second report call with srw.run_report ( or migrated version with hyper link )?
So the first control of input data is reported with the button/hyperlink for launching pl/sql procedure with transactions.
After the pl/sql stored procedure call the second output control report is launched to display the result of PL/SQL stored procedure.
0