We are talking about a capitalized D here!
No there are other errors as well, and they may be the cause of the
problem, which is why I highlighted them, but you seemed to take offence
to that.
My current XSL has the problem of not using key in a meaningful way
(always returns 0) and also produces a row for each Record, although
it does order them by type.
XSL goes something like:
<xsl:key name="options" match="option" use="@type" />
<xsl:key name="oldID" match="Record" use="disabPrimary" />
<xsl:variable name="$Definitions" select="Document(Disabilities.xml)"
/>
There are three errors in that last line, two are syntax errors that
would be reported by the xslt system (so I assume they are not in your
real code) so perhaps you had
<xsl:variable name="Definitions" select="document(Disabilities.xml)"/>
If so then the argument of document() is the node set of elements with
name Disabilities.xml which is empty so $Definitions will be empty which
may well cause you to not get the result you expect
or perhaps you had
<xsl:variable name="Definitions" select="document('Disabilities.xml')"/>
how are we to know?
David
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--