Well then, how much data are you talking about in the cursor? You'll basically need to pass that data up to the server (via a SP) and then do the join there and return the result set. There is an OPENXML option in the FROM clause, so you could convert your cursor to XML and pass the string as a parameter to a SP for the JOIN to happen there.

HTH,
Chad

>The first possibilty is a no go because we are talking about millions of records.
>
>The second possiblity, I would like to avoid creating the cursor INTO TABLE instead in order to prepare it for the SQLExec() INNER JOIN clause as it will create a file on disk.
>
>Basically, I would like to find a way to handle the cursor with a SQLExec() approach without having to create a file on disk.