> Is it possible to still further fine tune my XSL?(


You do an awful lot of

   <xsl:param name = "j"/>
 ....NODE2[$j]/NODE3

this means you are repeatedly searching for all the NODE2 children to
find the j'th. I didn't follow all the logic of your code but it looks
like instead of the j parameter you could pass in the Node itself and
so the above would become

   <xsl:param name = "jthnode"/>
 .... $jthnode/NODE3


Similarly

   <xsl:variable name = "count2" select = "count(NODE2[$j]/NODE3) "/>
...
  <xsl:when test="($count2 &gt; 0)"> 

forces the system to count all the nodes, whereas if you had gone

  <xsl:when test="NODE2[$j]/NODE3">

then the system would only need to check that at least one such node
existed.

  <img src="\pricing\images\treePics\downarrow.gif"

should be

  <img src="/pricing/images/treePics/downarrow.gif"

to be a valid URI (not that that would speed anything up:-)


David


_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list