Hi Nadya,

It's good indeed that you solved your problem!
But I remain confused as tothe source of the *original* problem. You indicated strongly that it was a 'macro length limitation' problem in your estimation. My confusion is that I would not think that you would get a "SQL command too complex..." message in that case, but rather a simple syntax error.

Can you clarify (just so that I can add to my list of oddities)?

Thanks,

Jim N

>Ed,
>
>>>>Again, putting the values into a cursor and using an IN (subquery) may help with some of the length issues. There's no limit on the number of records in a subquery AFAIK.
>>>
>>
>>Either that, or adding code to what you emit to convert your INLIST string into values used to populate a cursor, You aren't limited to what can be done in the scope of a single command - you can emit a fairly complex procedure, using conditionals, loops, or whatever else is needed to set up for the query, or massage the results before returning.
>
>Ok, I've changed my btcc_multilist to use advantage of cursor. Works fine.
>Thanks again for your ideas.