[Home] [By Thread] [By Date] [Recent Entries]
Jim,
Ken's solution is also a good one (assuming he wrote what he intended to write in his untested code ;-). Note that he's optimized for performance on the assumption the nodes are correctly ordered in the input. If they're not, his solution will be slow on large datasets compared to mine, but it has the advantage of not caring how many levels deep you have to go. (Except for the output element naming bit: tricky, that. If you could name them 'Level2Category' instead of 'LevelTwoCategory', etc., this problem would go away). Cheers, Wendell At 04:49 PM 3/26/2003, he wrote: Untested but try the following approach ====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ====================================================================== XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|

Cart



