Subject: RE: [xsl] Building XML DOM from Access DB column with mixed content From: "Michael Kay" <michael.h.kay@xxxxxxxxxxxx> Date: Tue, 13 Nov 2001 17:23:17 -0000 |
You've got an impedence mismatch, trying to use a tabular data model on disk and a heirarchic one in memory. Get yourself an XML database :-) Mike Kay Software AG > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Doug Howell > Sent: 13 November 2001 16:38 > To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] Building XML DOM from Access DB column with > mixed content > > > Do any of you have any direction for me on this problem: > > I have a glossary.xml file which I've been parsing and > transforming on the > IE 5 client. Now, for a test, I'm implementing it via an ASP > page, parsing > and transforming on the server, and storing the glossary in an Access > database. I'm building a DOM, transforming it, then including > the string > result into the document. I've got the mechanics of it > working, but I've run > into a problem. If one of you could steer me in the right > direction, I'd > really appreciate it. > > I'm storing several of the XML elements in their own columns > in the Access > DB ("term," etc.). The trouble is that the "definition" > element has child > elements which I'm not breaking out into their own columns. > In other words, > the Definition field in my DB has child elements (such as > "<em>," "<uri>," > etc.) within it, as well as entity references. This means > that when I create > a "definition" element from the Definition field, the embedded child > elements and entity references are not parsed like they were > in my XML file, > but are treated like text. > > Is there a way to parse the contents of the Definition field > "on its way" to > the DOM document, so these elements/entity refs will be transformed > correctly to the HTML output? > > Thanks, > Doug Howell > > Here's part of the code: (I'm using MSXML3 SP1) > > <% > 'create XML doc from SQL results > dim root > dim entry > dim newElem > dim newAttrib > dim i > > Set root = gobjXML.documentElement > > i = 0 > While Not objRS.EOF > Set newElem = gobjXML.createElement("entry") 'create a new entry > root.appendChild newElem > Set newElem = gobjXML.createElement("term") 'create the term element > root.childNodes.Item(i).appendChild newElem > root.childNodes.Item(i).lastChild.Text = objRS("Term") > Set newElem = gobjXML.createElement("definition") > root.childNodes.Item(i).appendChild newElem > root.childNodes.Item(i).lastChild.Text = objRS("Definition") > i = i + 1 > objRS.MoveNext > Wend > objRS.close > objConn.close > Set objRS = Nothing > Set objConn = Nothing > 'do the transformation and write the results into the page below > strResult = gobjXML.transformNode(gobjXSL) > > %> > > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Building XML DOM from Access , Doug Howell | Thread | RE: [xsl] Building XML DOM from Acc, Chris Bayes |
Re: [xsl] using variables and attri, David Carlisle | Date | [xsl] Call context within a named x, Jeff Beadle |
Month |