>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 ---
>

Thanks, Rick. Does that mean if I am only using your XML classes for converting Fox cursors to/from XML that I don't really need to install XMLDOM?

I would like to try to avoid the hassles of having an incorrect version of MSXML installed on the end-users system, especially if M$ is dragging their feet on releasing the fix. For right now, all I need is the cursor/XML capability, not the object stuff.