A simpler solution is to use a Connector Loop with your Lookup
Connector attached. Then you get the following:

1. Components you drop under this loop are cycled through, once for
    each entry found by your Lookup Connector.

2. You get a Connector Parameters Map tab where you can map in
    the SQL you want to use. This makes it easy to use JavaScript
    or Expression mapping to compute this SQL string using values
    in Work Attributes or script variables.

    And if you are using a Loop and setting the SQL SELECT yourself, I
would
    use Iterator mode instead of Lookup. These two modes are almost
identical,
    apart from a couple of major differences:

       a1). Iterator mode leaves the result set on the server,
returning a single
              entry with its getNextEntry() call for each cycle.
       b1). Lookup mode fetches the result set in memory. To prevent
              memory problems, this is limited to max 10 entries &
configured in
              the AssemblyLine Settings tab -- called "Config" in TDI
6, and
              behind the AssemblyLine's "Options" button in TDI 7.
This can be
              set at the individual Connector level in TDI 7 through
the
             "More" button to the right of the Inherit From Parent
button.

       a2). Iterator mode uses Config parameters to perform its
search.
       b2). Lookup mode uses Link Criteria. The advantage here is that
the
              search is done during AL cycling, while Iterator mode
does this
              at initialization. However, since the Loop lets you map
in the
              Config parameters and set the Initialization option to
only Select,
              you get the same flexibility for Iterator mode.

3. You can step through this in the Debugger!!! (you knew I had to
    mention the Debugger as well :)

-Eddie

On Jul 2, 10:38 am, "kolev.kg" <kolev...@gmail.com> wrote: