Symptom
Run-time error LOAD_PROGRAM_LOST occurs when report output is
quit.
Reason and Prerequisites
During report output the editing program is loaded into the program buffer. If the editing program is changed by changing the report definition (Extras --> Definition --> Change) or by activating or deactivating form printing in the executed report and subsequently quitting report output, the editing program is regenerated. After the generation the program version on the database consequently no longer corresponds to the version in the program buffer.
As of Release 4.6, this new generation is carried out in a separate roll area thus preventing a conflict with the version stored in the program buffer. If the program was moved from the program buffer in the meantime due to a program buffer overflow, the program must be loaded from the database. During loading, the system detects that the program had already been loaded before and that there is a version conflict with the version previously loaded. For safety reasons, a termination occurs with error message OAD_PROGRAM_LOST to prevent inconsistencies due to an execution of the program with different versions.
Solution
You can ignore the runtime error in general since it no longer occurs when restarting the report output.
You can prevent the error message from occurring by taking the following measures:
o Make the program buffer sufficiently large so that the editing program is still completely contained in the program buffer when quitting report output.
o Do not make changes in the executed report but only using Transaction GRR2 or GR32.
Other terms
REPORTWRITER
No comments:
Post a Comment