>>Recently I've had to debug a few complex SQL statements. Is there any way to be able to determine - without having to remove pieces and rerun - what caused a SQL to return zero records? I think it should know, as it's whats pulling all the data together, but I haven't been able to find anything.
>
>Jay,
>
>First places I would look would be:
>
>1. Make sure that at least one record satisfies the WHERE clause.
>2. Make sure that there is at least one matching record for each INNER JOIN you have defined between two tables.
>
>Laterness,
>Jon

I actually understand why the SQL failed to return records, but only after debugging it. I was hoping there was a way that the SQL engine could tell me itself. It knows when there is an error, can it tell me why it returned zero records too?