Very Computer

Hi all,

Has anyone detected problem with the following embedded statement
EXEC FRS inquire_frs frs ( :VL_Cmd = command ) ; ?

I have just recompiled a function ( that did work fine on HP 10.01 ) and now
VL_Cmd contains 0 ( undefined ) when focus automatically goes to NextField
at the end of the current field ( I seem to remember that the correct value
is 4 for that event ).

Did I miss something ?

Our configuration is Ingres 6.4/06 patch 5506 on HP.UX 10.20.

TIA

Christian

Quote:>Has anyone detected problem with the following embedded statement
>EXEC FRS inquire_frs frs ( :VL_Cmd = command ) ; ?

>I have just recompiled a function ( that did work fine on HP 10.01 ) and now
>VL_Cmd contains 0 ( undefined ) when focus automatically goes to NextField
>at the end of the current field ( I seem to remember that the correct value
>is 4 for that event ).
>...
>Our configuration is Ingres 6.4/06 patch 5506 on HP.UX 10.20.

Well, autotab would return 12, but zero isn't right.  Are you issuing
the INQUIRE_FRS right after entering the activation block?  There are a
number of FRS functions that appear to smash the value of INQUIRE_FRS FRS
COMMAND, but I don't have a list of them.
I'm not familiar with that version+patch so I don't know if you've hit a bug
or not.

Karl R. Schendel, Jr.

Ingres and Unix Expertise

Past President, North American Ingres Users Association