So, to be clear, in the database painter, you executed 100 SELECT statements at once, so that all the results sets would load up into the painter, and before it finished, it blew up. Does this sound right?
If this is the case, my first impression is lack of surprise. Without more information, it seems like running out of memory might be a reasonable assumption. Or, that the painter wasn't meant to load 100 panes of output all at once, and died. (I would imagine these results might be PB version or DBMS-specific, but I just loaded 100 "SELECT 1" statements in PB 12.5's database painter against ASA with no problem.) Or, maybe one of the statements ran into problems which PB would normally be able to handle, but with the load on the IDE, it choked and died; you haven't said if these statements execute successfully when run independently. It could be a lot of things.
In terms of "resolving the issue", it's not clear what the problem is. One solution might be to execute these one at a time, dealing with the output between each step. If the objective is to execute these all at once (e.g. for time sensitivity), I'd look outside PB at something that didn't try to load all the results into memory at once, like ASE's iSQL command line utility (you could easily create a .BAT file to spool these into .TXT files). And, if you've got PowerBuilder sitting in front of you, you have the means to create a tool that does the job if you need to do something "only" PB does, like saving to Excel.
Good luck,
Terry.