Shamil Salakhetdinov
shamil at users.mns.ru
Thu Nov 16 13:39:56 CST 2006
<<< Although maybe breaking it down first by the < /> and then looking inside each of those... >>> Greg, The simplest and the most effective and safe practical approach is to use MSXML's DOM for relatively small XML files and MSXML's SAX API for large XML files. I'd recommend not spending your valuable time trying to parse XML files using custom code - that's not a trivial task for a general case. And because you say that the party which supplies you with this XML file has almost no idea "how they make it" then custom parsing approach looks even more risky... -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Greg Smith Sent: Thursday, November 16, 2006 10:18 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Parsing XML as a string? John: Yes...I want a lot of the enclosed < /> fields, but I also need them with respect to their description, such as the FEES, of which (in this example) there are 5, each with it's own description "StandardFee", etc. So I'll not only need to get the data, such as the fee, but I have to be able to delineate which fee it is so it can go in the right table field. For all practical purposes, I can ignore anything after the start of the <DOCUMENT> because there's no data past that point. And you are also correct in that this doesn't fit today's standard xml format. I've even asked the people who are sending it to me just WHAT type of xml is it, but not gotten an answer...which makes me believe they don't know either. It works for what they want, so don't mess with it I guess...and, of course, out of 99 counties, mine is the ONLY one using an Access db program to do the Recorder's work (so far... :)). You'll note that some of the Elements (Fee) have two attributes, whereas some of them (Grantor) have many more. So a rule that says only get the two would not work in all cases. Although maybe breaking it down first by the < /> and then looking inside each of those... Greg <<< tail skipped >>>