|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] 1 condition OK, adding a second blows it up
Another one that has caused me grief.. This works <xsl:for-each select="//employee[(./@department = $deptName) and (./approvals/approval[@timestamp > $filterFDate])]"> However, when I add a second condition it fails <xsl:for-each select="//employee[(./@department = $deptName) and (./approvals/approval[(@timestamp > $filterFDate) and (@timestamp < $filterTDate)])]"> as does this permutation <xsl:for-each select="//employee[(./@department = $deptName) and (./approvals/approval[@timestamp > $filterFDate]) and (./approvals/approval[@timestamp < $filterTDate])]"> $filterFDate and $filterTDate are both defined. The escaped versions of < and > also fail. Allistair Crossley Senior Intranet Developer QAS Ltd Direct Dial: 020 7819 5343 <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com">www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








