Just as a final note for this Stored Procedure...Both Sachin Nandanwar and mister.magoo's advice worked here (the original advice that I thought didn't work actually did end up working once I added the version number change to line 163). A hybrid of the two (simply switching out the COMPUTE SUM line with the SELECT statement), and the change to line 163 has produced the best results for me thus far.

This report is something I do not schedule so I am not as concerned over the SQL Injection attacks mentioned earlier, but best practices definitely dictate that as a needed change, if/when this becomes more automated.

Than you both again for your assistance in helping me get this to work.