09-25-2013 09:37 AM
Unfortunately this is not a good solution.
You autoindex the input-array. For every input you generate an output.
What do you do with the elements that do not match?
I'd expect a cleaned array at the output, with a reduced number of elements.
Using LV2012(and up) you may qualify the out-index to include only matching elements.
Pre-2012 you would have to start with an empty array and insert what is to make it to the output.
(Check examples for LV 2012)
Gabi
09-25-2013 10:23 AM - edited 09-25-2013 10:27 AM
@GabiTillmann wrote:
Unfortunately this is not a good solution.
You autoindex the input-array. For every input you generate an output.
What do you do with the elements that do not match?
I'd expect a cleaned array at the output, with a reduced number of elements.
Using LV2012(and up) you may qualify the out-index to include only matching elements.
Pre-2012 you would have to start with an empty array and insert what is to make it to the output.
(Check examples for LV 2012)
Gabi
i did realize that hoping the OP will manipulate accordingly without me doing that....here ya go anyways...
09-25-2013 11:34 AM
No nit picking...
I include ya version in LV 2013, which I think should work.
One the traditional way. You have to provide a means to skip non matching strings. That why you need the case.
Second the new way with conditonal indexing.
Hope it helps.
Gabi