I started to build wwXML with features to avoid the parser, but it was very, very slow doing the imports.

Also, given the fact that the XML standards are constantly changing and that encoding/decoding needs to be part of any XML solution I decided not to go that route.

MSXML is fixed - MS just has not released the damn thing because not enough people are complaining in the newsgroups (mainly because VB ignores the error).

For the record, Object imports can work without XMLDOM if the objects are flat (ie not hierarical).


+++ Rick ---

>>Fred,
>>
>>MS XMLDOM can be seperately installed see the page http://msdn.microsoft.com/downloads/tools/xmlparser/xmlparser.asp. Make sure you use the IE5.0 version and not the IE5.01 version.
>>
>>>I've already got and use those. They depend on IE (or at least XMLDOM). Thanks.
>
>
>OK. Just how are you sure you've got the right version? I think I saw that Rick Strahl said there was a problem with the released version in W2000. Is that what you're warning me about? This is the main reason I DON'T WANT TO install another .DLL or whatever, so crap like this won't happen! Thanks for the heads-up, Dave.