>>>Nope. The only alternate is to put all the possible values there:
>>>
>>>in ('val1', 'val2', ...)
>>
>>OK. Is there any documention on what you can put in there? Like the IN, EXISTS, ALL, and ANY or SOME? The select-sql topic in doesn't mentioned any of them, and the HG mentions but doesn't explain how they work.
>
>I liked the JOIN solution better, but you have to put actual values there and no wildcards. This is the same as doing:
>
>where field1 = 'val1' or field1 = 'val2' or ...
>
>which is the same as VFPs inlist(field1, 'val1', 'val2', ...)
>
>You should be able to do:
>
>in (?lcVal1, ?lcVal2, ?lcVal3, ...)
Yep, I had thought about that but there are potentialy hundreds of values in the list of Tasks. Using "where in" is working fine.
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!