I fathom that Rapid SQL is the tool you're using to develope your SQL
statements ...

The message you see in Rapid SQL is a warning message, not an error
message, so the message is benign.

If you're getting the message in Excel, I'm not clear on how you're
seeing it. Where does it come from? Are you using MS Query by any
chance?

The first few in the series insert data into a DB2 database. (in SQL writing
code program like Rapid SQL returns a message like "13620 row(s) affected.".

Then:
I can return data, but I have not figured out how to handle the success
message. I even created a temporay sheet for the 'Success' to post. The SQL
jams trying to bring back the results.


We need to see the SQL to get a grip on why our SQL would hang.

Also, note that there is a limit to how long a SQL statement can be
that depends upon your driver. If you're attempting to insert over
1000 records in a batch SQL statement you're probably creating strings
that go beyond what either Excel, the DB2 driver, or DB2 can handle.

Respond with a SQL statement if you want more help.