XML problem - anyone got ideas?
Ok,
I like that AW support XML for datasets. But, here is my problem:
And, since I'm gonna screw up the terminology, bear with me:
I might have a data set like:
<company>
<name>456</name>
<phone>456</phone>
</company>
<company>
<name>123</name>
<address>123</address>
<city>123</city>
<phone>123</phone>
</company>
Which, is valid in an XML file. Now, if I read this into an AW grid and display as columns "Name", "Address", "City", "Phone" ... I'd think it would be able to display the records correctly (2 rows). But, it doesn't. It actually screws up the columns/rowdata.
I don't have control over the XML dataset. All I can do is read it in from the server.
Does anyone know how to get AW to account for missing data, assign the values correctly (possible based on TAG) and negate this issue?
AW is a good tool ... but I think, unless I'm missing something - if I am, please yell, the XML support does need a little work.
I like that AW support XML for datasets. But, here is my problem:
And, since I'm gonna screw up the terminology, bear with me:
I might have a data set like:
<company>
<name>456</name>
<phone>456</phone>
</company>
<company>
<name>123</name>
<address>123</address>
<city>123</city>
<phone>123</phone>
</company>
Which, is valid in an XML file. Now, if I read this into an AW grid and display as columns "Name", "Address", "City", "Phone" ... I'd think it would be able to display the records correctly (2 rows). But, it doesn't. It actually screws up the columns/rowdata.
I don't have control over the XML dataset. All I can do is read it in from the server.
Does anyone know how to get AW to account for missing data, assign the values correctly (possible based on TAG) and negate this issue?
AW is a good tool ... but I think, unless I'm missing something - if I am, please yell, the XML support does need a little work.
Carl
May 2,