Okay, folks, I got 3 Q's f/today. Here's the first. Can y'all tell me
about general issues related to EXITFORM? One of you - I apologize in
advance f/not naming who it is - kindly advised me on this topic a couple of
weeks ago, but I think I'd like to know a bit more.
Here's why I ask. I've been using EXITFORM in an FXP in a form and it has
worked just fine. Control of flow/execution is then handled by this FXP and
other called routines. One or more of these may "ENTER USING ..." with one
or more other forms. Now, one of these other forms also has an FXP w/an
EXITFORM. Every time it executed, the system (RBase in toto) went to La-La
land, like it was in an infinite loop or the instruction pointer went 0xNULL
or something ... I have removed the call in FIELD SETTINGS and replaced it
w/BTN that "Exits" form, and, while this works, it requires an extra step or
two for the user that I'd rather not have in the work-flow.
The only noticeable difference is that the mis-behaving IF-THEN block was as
follows :
-- This form has VARIABLE fields ONLY
-- that are processed upon/after exit
-- This is just to leave it quickly & easily
-- (comments added f/this e-mail)
SET VAR vLastKey = (LASTKEY(0))
IF vLastKey IN ("[ENTER]","[ESC]") THEN
EXITFORM
ENDIF
RETURN
as opposed to a SWITCH(.vLastKey) or a single condition IF-THEN block.
Next Q is coming.
Thanks,
Steve in Memphis
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
