Maybe your terminology is wrong, but the xml/db tool is for creating an XMAP not an extraction (EXT) The xmap is for mapping data from a DB file to an XML, the EXT is the other way round.
Personnaly i would do the EXT code manually, it gives you a better understanding as to what is going on. The documentation in the unibasic extensions manual is fairly good on this, the only tricky point is the insertion of commas into the xpath for the position of multi and sub values. rgds Symeon. On 04/12/06, David Wolverton <[EMAIL PROTECTED]> wrote: > > Well, it tells me I have to 'build an EXT file' - and I guess that's > manually - which was my question. So why did IBM bother with the XML/DB > tool if it only builds half of what you actually need to handle XML files? > That sort of thing really annoys me! All my testing with the XML has been > with items where I 'hand built' the XML strings, and I was ready to start > building and receiving them from UniData records - but all the work I did > for the XML mapping using the XML/DB tool didn't construct EXT files - > just > seems like IBM dropped the ball way short of the goal described for the > tool! > > Am I the first person to notice this, or has this issue been turned in to > IBM? Or am I just missing some feature of the XML/DB Tool? > > DW > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Brian Leach > > Sent: Monday, December 04, 2006 3:36 AM > > To: [email protected] > > Subject: RE: [U2] Creating XML Extraction File > > > > David > > > > Here is a simple example (UV syntax, adjust for UniData accordingly) > > > > Hope this makes sense. I'll turn it into a knowledge base > > article when I have time. > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
