(Folks, I'm resending this email since it was bounced back to me before.
Outlook problem I think....)
OK, so it's easy enough to store flat XML structures in an SQL database:
The above is a simple example of the standard data record structure that
easily spills out into a table format or whatever.
My problem arises when you have complex, irregular XML. Example:
<Name>The Deposits Window</Name>
<Para>When you enter payment information into one of the payment receipt
windows, such as the <Bold>Receive Payments window</Bold>), you can
immediately <InTextField>Deposit to Account</InTextField> or
Undeposited Funds</InTextField>. If you decide to
Account</InTextField>, the system automatically deposits the funds
bank account you select. However, if you decide to
Undeposited Funds</InTextField>, the system builds a list of
for you to review and deposit into an account.
You notice in the above example that there are bunches of random tags that
may or may not appear within another tag. Some of these subtags are used
simply for XSL visual styling purposes, and some are used to tag information
for searching. It doesn't fit into the standard Table/columns/rows type of
If I have a DTD that I use to create this type of content, how can I store
this information in an SQL database? Do I just need to work with 'chunks' of
I work in a Microsoft shop with current Microsoft tools... so any help to
that end would be appreciated.