Hi all

I didn't know how to name this thread, thus an odd one.

Here is my code from the init of the screen:

m.typefilt = "INLIST(a09macct.typegroup, "CASH", "BANK")

this is the code in the valid of an invisible button:

invhelp(paras, ..., m.typefilt)

this is the code in invhelp():

PARAMETERS m.zparas, ..., m.zfilter
...
IF m.zfilter # "NOCHANGE"
   SET FILTER TO &zfilter.
ENDIF
...

This above works well. Now I ended up with a requirement wherein the typegroup can contain a word and not necessary at the start of the field. So I wrote a udf to tackle the same which just does a $ for each and every parameters passed to the UDF so the inv. button call changed to:

Here is my code from the init of the screen:

m.typefilt = "typgrp(a09macct.typegroup, "CASH", "BANK")

This above started giving me errors so I changed the inv. button code to:

invhelp(paras, ..., &typefilt.)

Great works for a screen, but the second screen gives an error, why?

Because in the second screen the same inv. buttons valid codes interprets the string m.typefilt and sends either a .T. or .F. to the invhelp() function.


Please can anybody shed some light on what might be happening. Switch back to INLIST and all previous code works.