Thi issue is just about closed. Thank you Jel, you deserve a star for waking me up on a few things.
First of all, your help on creating a node list and passing it works like a charm, Here is an example of doing it for all values:
HERE
I had also at one time successful wrote the ASP to convert the original XML to another XML doc, and then passed through to a transform doc to change to HTML; however, I still had some limitations and the server side work had to be tremendous.
My final problem deals with "grouping". I have added 4 sort lines after the for-each:
Code:
<xsl:for-each select="//weeknplayer[compareID=$IDs/*]">
<xsl:sort select="YEAR" order="ascending" data-type="number" />
<xsl:sort select="TRIMESTER" order="ascending" data-type="text" />
<xsl:sort select="WEEKNUMBER" order="ascending" data-type="number" />
<xsl:sort select="*[name()=$SortField]" order="{$SortOrder}" data-type="{$DataType}" />
This creates output such as:
SUMMER 2002 Week 1 Healy,Mike 4 ...
SUMMER 2002 Week 1 Tierney,Brandt 3 ...
SUMMER 2002 Week 2 Healy,Shawn 5 ...
SUMMER 2002 Week 2 Flatbush,Nick 6 ...
NOw I would like to add a header for each time the SUMMER, 2002, or Week number would change. I have tried this:
Code:
<xsl:if test="preceding-sibling::weeknplayer[1]/compareID != compareID">
<tr>
<td><xsl:value-of select="YEAR"/></td>
<td><xsl:value-of select="TRIMESTER"/></td>
<td colspan="2"><xsl:value-of select="WEEKNUMBER"/></td>
</tr>
</xsl:if>
But it doesn't seem to apply itself on the output, but during the processing, which is influenced by the sort, or it is to strictly based on node positioning, which isn't what actually prints out.
Any ideas folks. At current I am thinking I need to go back to a dual process, which would allow me to re-order the XML on the first process, and then the physical pressence check would work on the second (I think). But this would not be desired as such.