On 4 Apr, 06:57, "Dimitre Novatchev" <dimit...@tpg.com.au> wrote:
> Seems you are actively cross-posting.
>
> Not only is this a sign of lack of self-confidence, but it is creating
> redundancies that lead to typical anomalies -- in this case a waste of time
> for the readers of the newsgroup and the .NET forum.
>
> Or probably you are not trusting the people, who answer your questions (if
> this is the case, do not ask questions, in the first place!)?
>
> Stay assured that you may have full confidence in an answer by Martin Honnen
> (or by me) about an XSLT problem.
>
>   :o)
>
> Cheers,
> Dimitre Novatchev.
>

I do apologise for cross posting.

It was not in any way a reflection of Martin's replies, which have
been excellent. Purely trying to make a deadline and asked two places
in hope of getting an answer sooner.

Martin; thanks for your help, its now working as inteded.

One more ting, just so I get a greater understanding of the code.

The bit below, makes a sorted copy of the computer element and
children elements (attributes included) to the variable rtf?
<xsl:variable name="rtf">
<xsl:for-each select="computer">
        <xsl:sort select="@number" data-type="number"/>
         <xsl:copy-of select="."/>
</xsl:for-each>
</xsl:variable>

Unsure of the below code, it seems to convert the above 'tree-
structure' to a node-set. What does a node-set entail? Does that
enable one to traverse (for-each) the structure?

<xs:variable name="sorted-computers" select="msxsl:node-set($rtf)"
    xmlns:msxsl="urn:schemas-microsoft-com:xslt">


The final bit of code, is $Sorted-computer pointing to the root
element and therefore you need to specify further by adding /computer?
I thought the rtf variable only contained "computer" elements, so why
the need for /computer?
<xsl:for-each select="$sorted-computers/computer">


Again, thanks for helping.