sheridan101
Programmer
I am sick of this error!!!! If a report is attached to a stored procedure, and ANY INSERT...SELECT... query within the procedure inserts no records, this error WILL result and the report aborts!!!! The same results from trying to perform a RTrim()/MAX/MIN on a NULL produced by a Join, which is also a non-fatal query condition that does not cause the query to terminate. IS THERE A WAY TO TURN THIS OFF AND ALLOW THE REPORT TO FINISH WITHOUT HAVING TO DUPLICATE THE QUERY TO COUNT THE NUMBER OF RECORDS IT WILL RETURN FIRST??? THIS WASTES TIME UNNECESSARILY!!!!!
Ultimately, what I want to do is insert the data from the query into a temp table variable. If there were 0 records inserted, then insert a dummy record for processing, or in some cases, simply produce an empty report. If I execute the stored procedure by itself through Query Analyzer, this process works perfectly. However, because INSERTING 0 records seems to generate a non fatal internal query error, Crystal detects this condition and generates this stupid error in response, terminating the report every time, and I am fed up with it!!! It is THE most useless error because it also tends to mask other more serious errors that a stored procedure might generate!!!
Ultimately, what I want to do is insert the data from the query into a temp table variable. If there were 0 records inserted, then insert a dummy record for processing, or in some cases, simply produce an empty report. If I execute the stored procedure by itself through Query Analyzer, this process works perfectly. However, because INSERTING 0 records seems to generate a non fatal internal query error, Crystal detects this condition and generates this stupid error in response, terminating the report every time, and I am fed up with it!!! It is THE most useless error because it also tends to mask other more serious errors that a stored procedure might generate!!!