Bonjour,
So you mean that, when I want to avoid EX &TOTO or -INCLUDE &I_LL_KNOW_LATER,
that any how MR will reject, by using this Stackhanoff's trick :
I get all the possible Focexecs be moved ...
*-SET &ECHO=ALL;
-DEFAULTS &REQUETE = 'VIFSTCRE', &TYPSOR = 'H'
-PROMPT &REQUETE.(VIFSTCRE,VIFSTENS,VIFSTCRC,VIFSTCRO,VIFSTGRO).Requête.
-PROMPT &TYPSOR.(H,X,W).Type de Sortie.
-* -TYPE &REQUETE
- IF &REQUETE EQ 'VIFSTSIT' THEN GOTO :VIFSTSIT
-ELSE IF &REQUETE EQ 'VIFSTCRC' THEN GOTO :VIFSTCRC
-ELSE IF &REQUETE EQ 'VIFSTCRO' THEN GOTO :VIFSTCRO
-ELSE IF &REQUETE EQ 'VIFSTCRE' THEN GOTO :VIFSTCRE
-ELSE IF &REQUETE EQ 'VIFSTENS' THEN GOTO :VIFSTENS
-ELSE IF &REQUETE EQ 'VIFSTCRP' THEN GOTO :VIFSTCRP
-ELSE IF &REQUETE EQ 'VIFSTGRO' THEN GOTO :VIFSTGRO
-ELSE IF &REQUETE EQ 'VIFSTBQE' THEN GOTO :VIFSTBQE
-ELSE IF &REQUETE EQ 'VIFSTSIG' THEN GOTO :VIFSTSIG
-ELSE IF &REQUETE EQ 'VIFSTTRT' THEN GOTO :VIFSTTRT
-ELSE IF &REQUETE EQ 'VIFSTCNF' THEN GOTO :VIFSTCNF
-ELSE IF &REQUETE EQ 'VIFSTGSI' THEN GOTO :VIFSTGSI
-ELSE IF &REQUETE EQ 'VIFSTSPE' THEN GOTO :VIFSTSPE
-ELSE GOTO :PASTROUVE ;
-:VIFSTSIT
-INCLUDE app/vifstsitw.fex
-EXIT
-:VIFSTCRC
.../...
I recognize that by this scholar_Level_0 Menu is not very clever ( I want to know who is doing what, and when ...) .
But that a pre-parse by MR causes such a big trip surprises me too.
I very much like DM, on any Focus machine, and not too much of this repository and Pre-Parse ...
!ibi.amp.TOTO has not yet fully replaced &TOTO in my mind.
*** From now on, this message turns to a bit of strange ( AP only) ***
Of Course, WINFORM and HTMLFORM are different.
Just as TSO (Synchrone) and IMS (asynchrone) are different.
Except that IMS can have some Scratch Pad Area saved and be driven so that the End-User will never know the difference
between synchronism and asynchronism.
How to handle a context with a couple of HTMLFORMs was my question.
And DataBase Oriented as I've been for so many years, the Global Variables won't suit me.
A long, long time ago, I told Stephane CHABREL all that I thought of this damned Focus Langage
that, sometimes requires semi-column and sometimes rejects them.
that sometimes pretends that OR and AND are exactly the same, and sometimes kills you if you change OR into AND
that indicates Errors Near or At Line xxxx
(I apologise for that: Focus is very clear, regards to some DB2 Utilitarians that don't even try to help)
Stéphane kidded me (I was responsible for a Focus Site at the time).
And, then, he gave me a few keys I've never forgotten to keep in touch with Focus's mind and soul
I was the other side of the mirror ...
I now again need this kind of friendly help to really enter into the DS/WebFocus world (Might be from a book, but which ?)
But not only : You stupid, how can you ?
Matter of Factedly, Stupid I am, but not so ignorant as you might think
I need to get through some kind of frontier, and it's not so easy.
And, above all, I want to build a new Focus layer above existing Focus layers.
Focusely and Cordially
Focus Mainframe 7.6.11
Dev Studio 7.6.11 and !!!
PC Focus, Focus for OS/2, FFW Six, MSO