Altova Mailing List Archives

Re: Let me rephrase the question ...

From: "Danny J. Lesandrini" <dlesandrini@-------.--->
Date: 8/8/2003 8:19:00 AM
Thanks for the vote of confidence.  I'll stay with what I've done.

It just seems kludgy to hard code ordinals for child nodes.  I'd
have rather called them by name, like you can with recordsets.

   rst.Fields(0) = rst.Fields("PRBLM_ID")

But, it doesn't seem like you can do that with the XML DOM object.
I guess that's part of the contract with sharing data using XML.  We
all agree to stick to a schema ... right?  Hope it works that way in

Thanks for your help
Danny J. Lesandrini

"MSFT" <lukezhan@o...> wrote in message news:Uv9ywFXXDHA.1724@c......
> I think your way is one of the good solutions for such a problem. If you
> want to know other ways, you may take a look at Xpath query, here is a
> sample for it:
> HOWTO: Use XPath Queries in MSXML DOM selectNodes Method
> For more information on XPath, you can refer to MSDN:
> xpath_ref_overview_0pph.asp
> Luke
> "Microsoft Security Announcement: Have you installed the patch for
> Microsoft Security Bulletin MS03-026?? If not Microsoft strongly advises
> you to review the information at the following link regarding Microsoft
> Security Bulletin MS03-026
> and/or to
> visit Windows Update at to install the
> patch.  Running the SCAN program from the Windows Update site will help to
> insure you are current with all security patches, not just MS03-026."


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.