Jurij,

Thank you for your reply - insightful as always.

First, just to clarify, my reference to '2 levels of nesting' is the same as 'referencing the outer column in an in-line view'. I just look at it a little differently

You say that "that is not permited, you can never reference an outer query's column from an inline view. Never." This certainly seems to be what I have found. My question is : Why?

Firstly because it seems so obvious to me that it *should* work and secondly because you seem so positive that it *can't* work. Does it specifically say this somewhere in the documentation that I missed?

My reasoning puts correlated sub-selects on par with binds. Basically, for each row in the outer resultset, run this query and use the value of the current row for the 'bind' variable.

If I changed my non-working example from I.INDIVIDUAL_ID to :INDIVIDUAL_ID, it becomes a legal statement. Of course I get the wrong results, but following my reasoning, if they can see the bind down 2 levels why can't they see the correlating column down 2 levels and handle it accordingly?

I know, of course, that there's nothing you or I can do to change this, but it is *soooo* frustrating. I have been stonewalled by this 'error' (in my opinion) on enough occasions that I am really getting p****d off!

Sorry, venting over

Thanks,

- Chris