Well, I do have one other reason for using XML: flexibility in structure. What I have in mind doesn't fit a grid very well. I suppose I could split my BudgetClass up into separate header and detail structures, but it would basically mean restructuring my whole app. I would pretty much have to start all over. I have already written VB.NET code that takes advantage of 3.5 XML handling; I might post it in the near future. What it enables me to do is generate XML in my code using a combined XML/ASP format. I can use variables both as tags and as actual data; can you do something similar with SQL? If you saw what LINQ-to-XML can do, you guys might see than XML does have its uses other than SOA. I might make an SQL Server version at a later date... if I do it will probably be in C#. I know I probably seem like a maverick by now, but I'm not as married to the status quo as I would be as an established programmer. Thanks for the suggestions, but unless you show me how to replicate something like
<Budget>
<Header>
<ItemCount>2</ItemCount>
<AmountBudgeted>100</AmountBudgeted>
</Header>
<Details>
<Item Name="CDs">
<Percentage>10</Percentage>
<Amount>10</Amount>
</Item>
<Item Name="Books">
<Percentage>30</Percentage>
<Amount>30</Amount>
</Item>
</Details>
</Budget>
in one structure using SQL Server, I'll stick to what I'm using.
Ross
Lay a .NET over the world