setting up tables differently based on existance of xml tags. (static variables, recursion, templates, and intrigue)

Here's a (hopefully) interesting problem: (I've been editing this email every day. Every time I can't figure out how to do something, I come up with an alternate plan, assisted by a few people in #xml on irc.freenode.net. (Thank you Bebabo). I figured at this point I'd share my experiences. If

Re: setting up tables differently based on existance of xml tags. (static variables, recursion, templates, and intrigue)

Couple things: First, I'd dump this topic on the XSL list. Those folks love this kind of question, and they are good at helping with this kind of issue. Second, I'd look at making a key to hold the field-that-has-a-value-and-whose-next-sibling-has-a-value combos. Then, rather than read the

Re: setting up tables differently based on existance of xml tags. (static variables, recursion, templates, and intrigue)

Forgot to add the URL for the XSL list: http://www.mulberrytech.com/xsl/xsl-list/ Jay Bryant Bryant Communication Services robert frapples [EMAIL PROTECTED] 11/30/2004 03:09 PM Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject setting up tables differently based on