Re: int_flag in vdc

Mike Aubury <[email protected]>
Newsgroups gmane.comp.lang.4gl.aubit.general
Message-ID <CAGAq4WHtb0XEUd-u8mMSAz9y7cbYV8Uy6RCrumh0bYT4iUbCPg@mail.gmail.com>
Just to detect the issue - is it possible to try with the IF test outside
of the INPUT.
(It might be that the RETURN is failing to close something down in there.)
Something like :

FUNCTION a_input_arr()
   DEFINE f1 char(10),
          a_input_arr ARRAY[20] OF RECORD
            f2 char(10),
            f3 char(20)
          END RECORD

   INPUT BY NAME f1


   IF int_flag THEN
                  LET int_flag = FALSE
                  RETURN FALSE
   END IF

   INPUT ARRAY a_input_arr FROM s_input_arr.*
       ON KEY (F10)
             RETURN true

   END INPUT

   IF int_flag THEN
                LET int_flag = FALSE
                RETURN TRUE
   END IF


   return true
END FUNCTION


On 27 December 2016 at 14:24, Gerardo Valenotti <[email protected]>
wrote:

> Hello everyone
> I am doing a master-detail style test, when executing the int_flag in the
> input array does not execute the input again in the master field, the
> example works well in TUI but in VDC has that behavior, if anyone has a
> suggestion I would appreciate it.
> regards
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Aubit4gl-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/aubit4gl-discuss
>
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
Aubit4gl-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/aubit4gl-discuss
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.