Question Re: problem with call screen executable program in Technology Q&A

problem with call screen executable program

former_member635273 — Wed, 18 Mar 2020 07:53:51 GMT

i have executable program.

mycode.

START-OF-SELECTION.
  PERFORM f_check USING lv_flag.
  IF lv_flag IS NOT INITIAL.
    MESSAGE 'Can''t Print' TYPE 'E'.
    CALL SCREEN 1000.
  ELSE.
    PERFORM f_process_data.
    PERFORM f_show_smartforms.
  ENDIF.

after i run. screen stuck in blank like below.

I want back to first screen.but it's not work.

i hv tried CALL SCREEN 1000, CALL SCREEN 0, SUBMIT, but still stuck in blank.

Re: problem with call screen executable program

FredericGirod — Wed, 18 Mar 2020 07:59:38 GMT

did you try LEAVE TO SCREEN 0 ?

Re: problem with call screen executable program

former_member635273 — Wed, 18 Mar 2020 08:09:58 GMT

yes, but not work.

Re: problem with call screen executable program

venkateswaran_k — Wed, 18 Mar 2020 08:25:20 GMT

The error message shows : cannot print

Please debug in your f_show_smartforms.

Also, did you handle - BACK - usercommand in your GUI_STATUS ?

Regards,

Venkat

Re: problem with call screen executable program

former_member635273 — Wed, 18 Mar 2020 08:32:16 GMT

yes, I want after error message show, back to fisrt scrren. but stuck in blank screen.

Re: problem with call screen executable program

Dominik_Tylczynski — Wed, 18 Mar 2020 08:35:34 GMT

Hi saddam.id

You can use the following code:

START-OF-SELECTION.
  PERFORM f_check USING lv_flag.
  IF lv_flag IS NOT INITIAL.
    MESSAGE 'Can''t Print' TYPE 'S' DISPLAY LIKE 'E'.
    RETURN.
  ELSE.
    PERFORM f_process_data.
    PERFORM f_show_smartforms.
  ENDIF.

Best regards

Dominik Tylczynski

Re: problem with call screen executable program

former_member635273 — Wed, 18 Mar 2020 09:08:37 GMT

🙂 thnks sir. done.

Re: problem with call screen executable program

michael_piesche — Wed, 18 Mar 2020 14:39:28 GMT

1. MESSAGE TYPE 'E' will exit your report. CALL SCREEN is not even reached!
Use option 'DISPLAY LIKE' with statement MESSAGE to have different behavior but display it with same severity but not exiting your program logic:

MESSAGE 'Can''t Print' TYPE 'I' DISPLAY LIKE 'E'.

2. Depending on your defined screens and report coding, you might not even have to use the 'CALL SCREEN 1000' statement (In general Screen 1000 is the default screen when using an executable report, so imho, you shouldnt have to call screen 1000 because you are in screen 1000 (but it depends on your entire coding and report definitions).