Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

In module pool program dump due to ''too many consecutive nested call scree

Former Member

‎2008 Sep 08 11:08 AM

0 Likes
741

i got a dump i found that this is due too many consecutive nested call screens ,i have used call screen

statement in program ,in program once the transaction is completed successfully ,on pressing the ok button ,it will go to the first screen , here where the call screen is executed

so to prevent this dump what shall i do ,plz suggest

i got a dump i found that this is due too many consecutive nested call screens ,i have used call screen

statement in program ,in program once the transaction is completed successfully ,on pressing the ok button ,it will go to the first screen , here where the call screen is executed

so to prevent this dump what shall i do ,plz suggest

Reply
3 REPLIES 3
Read only

Former Member

‎2008 Sep 08 11:15 AM

0 Likes
680

clear ur question u want to break this nested call screen or u want to back at any screen

Read only

Former Member
In response to Former Member

‎2008 Sep 08 1:29 PM

0 Likes
680

yes i want to break the nested loops, so it would avaiod the dump ,at present the maximum number of nested screen levels is 50

Read only

Former Member

‎2008 Sep 08 12:21 PM

0 Likes
680

Hi,

Use LEAVE TO SCREEN 0 statement in OK code

Try this.