Did you even look at Peter's code, Vamshi?   Looks to me like it returns more than just depth... he even changed the title...

Nah... get too many right like this and you might "BE" a "Specialist"

Oooooh.... now I know we've got to work together, Remi 

I guess BULK INSERT and OSQL would be way to complicated, huh

Sure... I can see two levels like that... but N levels for invoices?   The only way I can see something like that happening...

With you?  You know the answer to that, Remi... ANYTIME.

Would be nice if you posted your solution so the rest of us can learn something...

Thats nice Dan... wanna share your solution?  Information does travel in two directions...

Between the join to the inserted table (which will cause the WHERE and ON clauses to be totally recalculated for every row inserted) and the correlated subquery in the WHERE clause,...

Heh... "Particle Physics for Dummies"

Heh... went to the doctor and said "Doc, if I raise my arm like this... it hurts".   Doctor said not to do that anymore

I agree... in SQL Server 2005, you could probably do it with a recursive CTE... But not in 2K.  Might be able to do it using a recursive UDF, but...

You bet... thanks for the feedback, Matt.

Ya do pretty darned well yourself, Lowell! You made a very useful tool.  I'm in the process of tweaking it for my own use and thought...

Nicely done, Lowell... you might want to check the ##Tmp table, though... the numeric datatypes always end up having a MaxActualLength of "0" and I think that's probably not right....