RE: Choose-When-Otherwise Nesting Problem

Thanks to Jason, Mike, and Matt!

It turned out that a close inspection of the XML *was* called for: another
developer had changed the XML content and eliminated our MaxAmount element.
Needless to say, I was trying to figure out what was wrong with the logic when I
should have been looking at what had gone wrong with the data. The system works
now!

To satisfy your curiosity, here is a sample of our XML.
-----
<transaction name="listAlerts">
    <useCount>134</useCount>
    <result>success</result>
    <status>complete</status>
    <tx>listAlerts</tx>
    <relativePosition>1</relativePosition>
    <alertDefinitionGroup count="13">
        <alertDefinition>
            <clientId>DEMOW00001</clientId>
            <activeFlag>(null)</activeFlag>
            <clientRelationshipId>DEMOW00001</clientRelationshipId>
            <AccountNumber>321</AccountNumber>
            <condAmt>(null)</condAmt>
            <alertType>Balance</alertType>
            <index>1</index>
            <deliveryMethodGroup count="1">
                <deliveryMethod>
                    <queue>true</queue>
                    <hourRangeMin>0</hourRangeMin>
                    <channelAddress>mrx@xxxxxxxxxxx</channelAddress>
                    <channelType>EML</channelType>
                    <deliverOnDays>YYYYYYY</deliverOnDays>
                    <hourRangeMax>23</hourRangeMax>
                    <seqNum>3</seqNum>
                </deliveryMethod>
            </deliveryMethodGroup>
            <MaxAmount>234.56</MaxAmount>
            <MinAmount>(null)</MinAmount>
        </alertDefinition>
     <ss>ListAlertDefinitions</ss>
    <listSizeLimit>100</listSizeLimit>
</transaction>
----

Thanks to Michael Kay for a great XSLT book. And thanks to everyone who lent a
helping hand! Our crew is staggering up the learning curve and this list is a
great resource.

Scott


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