| Hi Caroline,
I had the same problem and discovered that you cannot do the pre-check
and prevent the form from displaying. What you have to do is to do the
check in the named data that calls the form.
There have been a few notes in here that discuss how to prevent priv.
ALL-IN-1 users from calling a form, I can't remember the topic numbers.
In short it's not possible.
Regards,
Sunil
PS - saw your name and I nearly started singing the Neil Diamond song,
but than I had pity on my fellow CSC members ;0).
|
| G'day Sweet Caroline I never ..... sorry got carried away :0),
I think that the /PRE function executes after the form is displayed. I
only say this because of the tailoring I was doing many moons ago and
found that I could not stop the form from displaying. In my case which
is different from yours I had to use oaini.scp to setup symbols etc,
otherwise I had a few blank fields and had to press return to display
them on the main menu.
If you can let us know what are you trying to do we may be able to give
you some feed back and help you out.
Must go back to singing Neil Diamond songs now and picking up all the
broken glass ;-),
Sunil
|
| Hi Caroline,
It's amazing what I seem to keep in my head, this is from years ago,
/PRE='GET OA$FUNCTION="FORM " OA$MENU_PREVIOUS
\\GET OA$DISPLAY="Previous form displayed "'
will not display the called form but rather the one further down the
form stack. If there's no form stack then you'll get the main menu.
Neil Diamond, who's he ? I'm sure he's not in Faith No More
Oh yes,
Dave Wood
|