InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 05:20:42 GMT20http://www.sqlservercentral.com/Forums/Topic217493-176-1.aspxI'll have to tweek my own code as for some reason I was sure I could only have one parameter. Thanks for this.Tue, 11 Oct 2005 16:04:00 GMTLashamshttp://www.sqlservercentral.com/Forums/Topic217493-176-1.aspx<P>This seems needlessly complex - I just made a UDF that recursively calls itself with more than 1 parameter in my temp database and it works fine?</P><P>Example (and it's a silly one but it does work - it's 1am here!)</P><PRE>use TempDBGOcreate function recurse(@p1 int,@p2 varchar(10))returns varchar(8000)ASbegin</PRE><PRE>declare @result varchar(8000)</PRE><PRE>if @p1 = 0 set @result = @p2else set @result = dbo.recurse(@p1 - 1, @p2 + '.' + cast(@p1 as char(1))) </PRE><PRE>return @resultendGO</PRE><PRE>print dbo.recurse(5, 'X')</PRE><P> </P><P>I can see the benefit of the idea for some reporting purposes where you cannot have the tool work out how the hierarchy relates in client-side code, but if the entire hierarchy is being sent back to the client, you could also just send back the table and let the client sort out the display as well... Depends on the circumstances I suppose.</P><P>If someone is to implement in their DB/software, try rewriting without the messy string splitting for parameter passing - I don't see why it shouldn't work...</P><P>Cheers <img src='images/emotions/cool.gif' height='20' width='20' border='0' title='Cool' align='absmiddle'></P>Tue, 11 Oct 2005 09:38:00 GMTIan Yateshttp://www.sqlservercentral.com/Forums/Topic217493-176-1.aspxComments posted to this topic are about the content posted at <A HREF="http://www.sqlservercentral.com/columnists/slasham/reportingamenustructureusingarecursiveudf.asp">http://www.sqlservercentral.com/columnists/slasham/reportingamenustructureusingarecursiveudf.asp</A>Tue, 06 Sep 2005 22:34:00 GMTLashams