There's a barbaric parser, as well as an XML node toolkit, on PickSource.
Just go to downloads and look for the XML sub-group in the categories. The
simplest method for parsing XML is to break the document down by .
Well-formed XML will never contain a or character that isn't part of
an
Jeff,
Depending on the release of UniData 6.0, or 6.1 (7.? not sure haven't seen
it) the UniData preparation is some what different between versions:
UDT 6.0
You need to create a Extraction file definition
(see chapter(s) 10-Using UniQuery, or 14-Using Unidata the chapters
It's very easy to create/parse XML with .NET technologies. If you have a
schema then you can read an XML document, convert it into an ADO.NET
dataset in one statement, then you can push it into U2 very easily after
that with mv.NET or PDP.NET. UO.NET would take more work because it does
not have
Tony,
I'm interested, why not just use xslt to convert the XML directly into
a U2 string and then pass in the data using uodotnet subroutines. Is
there some advantage in using an extra step of converting to ADO?
Stuart
-Original Message-
It's very easy to
Stuart wrote:
Tony,
I'm interested, why not just use xslt to convert the
XML directly into a U2 string and then pass in the
data using uodotnet subroutines. Is there some
advantage in using an extra step of converting to ADO?
If you know xslt, xpath, xquery, etc, knock your
