RE: using attribute value as an attribute name OR usin

David,

Thank you veyr much; your code worked as advertised.

The column ordering is a concern. The sort simply does an alphabetic sort.
Somehow I need to apply the user's column selection order as well. I might
be able to convince the database gurus to rewrite their stored procedures to
return data as element values instead of attributes. Like so:

<row>
	<column1>r1c1</column1>
	<column2>r2c2</column2>
	...
</row

You seemed to think that would help?

Thanks again.

== Ross ==


-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of David
Carlisle
Sent: Wednesday, September 18, 2002 1:29 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  using attribute value as an attribute name OR using
element value as an attribute name





>     <xsl:for-each select="@*" >

you need the xsl:sort after this line othe rways you will get the columns
in a random order. The parser is _not_ obliged to report the order of
teh attributes, and XSLT is not obliged to preserve the order even if
the parser reports it. So if you want column1 to come out before column2
then you need to sort on name().

if you change @* to @*[key(...)] as in my last message, then only those
attributes that are listed in your config section will be used.


David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

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




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