Not sure to follow you
But how about using always the same big lookup, but using a smaller range for the FOR-TO-NEXT (i.e. Start @ different place, end @ different place)... then make some decision from there?
Not sure to follow you
But how about using always the same big lookup, but using a smaller range for the FOR-TO-NEXT (i.e. Start @ different place, end @ different place)... then make some decision from there?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I think I understood what you want to do. However, I do not think Lookup or even Lookup2 is suitable for this kind of thing. See, the Lookup2 statement expands into an assembly language macro with the parameters coded at 'compile' time.
Now, a possible solution could be to put the choices into an array. Everytime you pick one choice out of the array, re-pack the array after removing the chosen one. Use a little code to do what Lookup2 does and offer choices from the array.
Jerson
Bookmarks