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
Showing results for 
Search instead for 
Did you mean: 
Read only

SET/LEAVE/CALL screen?

Former Member
0 Likes
799

Hello All,

I have a problem. I have screen 1000 which contains 4 subscreens and I also have command button. When I press this button I have to pop up a screen (1007) with continue, cancel and hold button.

The problem is when I am writing a set screen 1000 when uses clicks cancel it is poping up screen 1000 in new window instead of leave to screen 1000. I had used SET/LEAVE/CALL screen to leave to screen 1000. I had specified 1000 as the next screen in atrritues of pop up screen (1007).

Please let me know why that is happening and how I can fix it?.

Thanks in Advance.

SDN

1 ACCEPTED SOLUTION
Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
777

Please use the following when user clicks cancel.

set screen 0.
leave screen .

Regards,

Rich Heilman

5 REPLIES 5
Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
778

Please use the following when user clicks cancel.

set screen 0.
leave screen .

Regards,

Rich Heilman

Read only

0 Likes
777

Hi Rich,

Please let me know what happens extactly when we use both of them set screen 0 and leave screen.

Thanks for response,

SDN

Read only

0 Likes
777
Read only

0 Likes
777

Hey! Rich,

could not grasp much. According to me Set screen 0. will take me to the screen where it is called from (screen 1000). But why it is giving screen 1000 in a different window.

Why is that i have to use leave screen. Please clear them for me.

Thanks

SDN

Read only

0 Likes
777

When setting screen 0, you are saying that you want to drop to the screen which the currect screen is called from, and you are simply leaving the current screen using the LEAVE SCREEN statement.

Not sure that I can explain it any better than that.

Regards,

Rich Heilman