Debbie, here are some screenshots showing the issue. In this case I purposely excluded a column from a Group By statement to demonstrate the issue.
Toad Data Point:
Here is the missing column
As you can see nowhere in the error trapping does it call out which Line/Column where the error is coming from. I am only presented with the Oracle error message. The last screenshot shows the Parser did not pick up on this either and there is not a red-X showing the error in the code. The error is generated when I try to run the SQL. I did verify I have the Tools option you gave activated.
When the same SQL is dropped into Oracle SQL Developer and I try to run I get an error like this:
As you can see in this case I am presented not only with the Oracle error, but the Line/Column position in the SQL code.
I just wanted to see if this is something that can possibly be considered for an enhancement for the SQL Editor or if there is something I am still missing.
Thanks again for your assistance.