Program dump

[Former Member]

Dear All,

There is a program where lot of custom containers and application toolbar buttons are being used. Sometimes after a few navigations like one screen to another it gives a program dump.

Can anyone tell if there is any method to be called to refresh the memory while navigating from one screen to another, so that it should never give a dump.

or any other solution to the above problem?

Regards

[Former Member]

What is the message in the dump?

If you are navigating screens using LEAVE to SCREEN, or SET SCREEN + LEAVE SCREEN, these add screens in memory to the screen sequence.

You might want to try using CALL SCREEN in some cases (e.g. when user executes the back function to the original screen), to reset the screen sequence and start a new one.

[Former Member]

Hi Mahesh,

Just know the different between Call screen and Leave screen.

Call Screen XXX: It hold the current screen and calls the XXX screen. So called screen also in the Buffer.

Leave Screen XXX : in this case , the current screen left from the buffer and New screen XXX will come into memory. so less momey consumbiton but when you click back it won't come to the previous screen because you removed it from the buffer. But in the case of the first one it won't happen.

Depending on this information you can change you report. So you can resolved the problem.

Warm Regards,

Vijay