not sure if this is a bug or a “feature”
I have a table A containing:
Arial
Arial Black
I have a table B containing:
Arial Black
I have a table C containing:
tabfindincol("A","$V","rc",0,0,"forward")
I then append an eval to B and use C as second input,
and I get 0
doing the same test with
Arial
Arial_Black
and B as
Arial_Black
obviously works and gives me 1
shouldn’t I be looking for “Arial*” in order to get 0 in the first case?
tx
d
we’ll call it a “feature” for now.
the problem is that tabfindincol uses spaces in its string pattern as its delimiters, so you are essentially searching for “Arial” or “Black” as $V expands. the way around it is to force tabfindincol to accept $V as a single argument, so using
tabfindincol("A",noevals("$V"),"rc",0,0,"forward")
will give you what you want. the difference is passing in
tabfindincol("A","Arial Black","rc",0,0,"forward")
or
tabfindincol("A","'Arial Black'","rc",0,0,"forward")
since in Touch, we sometimes want $V as multiple arguments and sometimes as just one, and there is no way to tell in advance, I don’t forsee a more intuitive solution any time soon. hope this helps.
Selina