StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20376608
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-04T13:25:04.663
FavoriteCount
0
LastActivityDate
2013-12-04T13:25:04.663
LastEditDate
LastEditorUserId
0
OwnerUserId
7585
ParentId
20356757
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You problem resolves around this line.... <pre><code> resultParent = resultParent + "&#xA;" </code></pre> Now, you are probably trying to output your XML like this: <pre><code><PARENT>George Aaron&#xA; Susan Lee Aaron&#xA; Richard Elliot Aaron&#xA;</PARENT> </code></pre> However, this escaped <code>&#xA;</code> entity is only relevant if the document has yet to be parsed. If it were a text document, that gets subsequent read and parsed into an XML document, then the entities would be handled as expected. But you are working with an XML document that has already been parsed. Therefore, when you do <code>resultParent = resultParent + "&#xA;"</code> it is actually going to insert a string of five characters into an existing text node, and because <code>&</code> is a special character, it gets escaped. Now, what you can simply do is this... <pre><code> resultParent = resultParent + chr(10) </code></pre> But ultimately this will prove fruitless because HTML doesn't recognise line-break characters, so you would have to write your XSLT to replace the line break with a <code> </code> element. If you wanted to do this in your VB code though, you could create new <code>br</code> elements yourself, and insert them <pre><code>For Each par As System.Xml.XmlNode In parentNodes currentParentValue = par.InnerText par.InnerText = String.Empty Dim parArray As String() = currentParentValue.Split(";") For Each Parent As String In parArray If Parent.Length > 0 Then Dim person As XmlText = objOutput.CreateTextNode(Parent) par.AppendChild(person) par.AppendChild(objOutput.CreateElement("br")) End If Next Next </code></pre> So, this takes the PARENT node, clears it down, then adds a text node, and new br element for each parent. The output would then be like so, which would be much easier to output as HTML using XSLT <pre><code><PARENT>George Aaron Susan Lee Aaron Richard Elliot Aaron </PARENT> </code></pre> (It shouldn't be too hard to add the br after every second parent if required). However, if may not necessarily be a good idea to put "presentational" information in a XML file. Suppose you later had to transform the XML into a different format? An alternate approach would be separate each parent into their own element. <pre><code>For Each par As System.Xml.XmlNode In parentNodes currentParentValue = par.InnerText par.InnerText = String.Empty Dim parArray As String() = currentParentValue.Split(";") For Each Parent As String In parArray If Parent.Length > 0 Then Dim person As XmlElement = objOutput.CreateElement("PERSON") person.InnerText = Parent.Trim() par.AppendChild(person) End If Next Next </code></pre> This would output something like this.. <pre><code><PARENT> <PERSON>George Aaron</PERSON> <PERSON>Susan Lee Aaron</PERSON> <PERSON>Richard Elliot Aaron</PERSON> <PERSON>Albert Smith</PERSON> </PARENT> </code></pre> Displaying this as HTML would also be straight-forward Hint: To display in groups of two, your XSLT may look something like this.... <pre><code><xsl:for-each select="PERSON[postion() mod 2 = 1]"> <xsl:value-of select=".">; <xsl:value-of select="following-sibling::PERSON[1]" /> </xsl:for-each> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhInserting line-break into XML so that it appears after XSL rendering in VB.NET
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim C
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.