Hi,
How can I call a CASE in one mnt file from othe mnt file? There is a CASE in maintain file mnt1. I just want to call that CASE from another maintain file mnt2 not the whole maintain proc mnt1. Please suggest.

Thanks.

This message has been edited. Last edited by: <Kathryn Henning>,

In the CALL to the Maintain Procedure pass the action you need to take, e.g.
CALL anotherMaint from myAction into myResult;

In anotherMaint retrieve the action:

MAINTAIN FILE filename from Action into Result;
declare Action/a20;
.
.
Case Top
.
selectAction();
.
EndCase

Case selectAction

If Action eq 'OneThing' Begin
  doOneThng();
  goto EndCase;
endbegin

If Action eq 'AnotherThing' Begin
  doAnotherThng();
  goto EndCase;
endbegin

EndCase

Case doOneThing
.
EndCase

Case DoAnotherThing
.
Endcase

END

Hi Alan,
Basically, I have to populate a stack in called maintain file based on user action (Click on Back Button on the form) in calling maintain file. Actually, this back button will take us to a form which is in called maintain file. On that form there is a Grid which is populated from a stack. I just have to refresh that stack on clicking BACK button.
Please advice.

Thanks,
Anil

Are you running a persistent or non-persitent maintain, i.e. Winform Show or Winform Show_And_Exit?

hi Alan,
I am using Winform show form_name.

Thanks.

So it is persistent, and any call has to go back to the Maintain that is displaying the Winform.

So clicking the back button will require navigation back to the Maintain you are in and then CALL the other Maintain and then get the data and display the form within it. You can directly call a Case that holds the CALL syntax to PROC2, but that is not the best practice.

This brings into question the issue of Form navigation.

For the sake of this, if you have a Maintain called PROC1 which calls PROC2, PROC1 has a form FORM1 and PROC2 has a form FORM2, then you appear to call PROC1, then PROC2 and display FORM2. Progress from FORM2 returns control to PROC1 and displays FORM1. At this moment there are 3 things that control the state of PROC2, how it was called, how it was ended and if the Winform FORM2 was closed. Then when PROC1 has user control with FORM1, pressing a button to return to PROC2 then leaves PROC1 with FORM1 open, unless a WINFORM CLOSE is issued, and where in PROC2 are you, that is, did you close the WINFORM in PROC2 prior to exit and was the process still alive.

If every time you call PROC2 the data needs to be refreshed, then the process is probably better closed cleanly and dropped. Then there is no problem with multiple open Winforms or data positioning. Next is the process of returning to PROC1 and what state that was left in.

Basically it can start getting complicated unless you manage the Winforms and the data positioning correctly. Multiple Winforms that are open may not immediately cause an issue, but there are examples of a driver process that ensures the Winform are opened and closed correctly. Every Maintain that has a Winform should have this driver procedure, and if followed correctly will allow you to go into and out of each maintain process correctly.