If we could perhaps return to constructive dialogue, could someone
please help me with the design that ties together my SQL with my XSL
presentation, and the XML between the two?

Initially I simply had my ASP document do the transform, however some
reports require additional (dynamic) information about each item.
Let's say I have 3 people, and each of them has 4 favorite foods and 2
favorite colors all stored in 3 separate tables.

My efforts right now are to use document() to call upon a server
script which dishes the results up in XML (foods or colors, in this
case). Is this a common solution? I do this because it I find ASP XML
manipulation to be difficult and I'd like to reduce ASP code so, in
the future, we can move to another language with minimal gripe.

Or does someone else recommend I simply build the XML tree entirely
within ASP before the transform?

On 5/30/06, Mulberry Technologies List Owner
<xsl-list-owner@xxxxxxxxxxxxxxxxxxxxxx> wrote:

To the list, sorry if I brought a squabble to public.  I saw no reason
to get a response in the nature that I received.

Steve, I hope you get the help you need.


Jon Gorman