The encoding attribute in the XML processing instruction is to indicate the encoding of the document, so it is likely that the document you are creating is not in that encoding hence the error. To check this look at the xml file you are creating in a hex editor, in utf-16 there are (at least) two bytes per character...

Use a repeating choice ordering group, eg for you examples

Without checking this out it may be because of the BSTR constructor you are using. BSTR's are unsigned short pointers, while you are passing in a const char* so a pointer cast is probably done (by the compiler) so two characters from your const char will be going into one character of the BSTR ie could be any character!! I suggest you try using CComBSTR, _bstr_t, or SysAllocString (and a matching free) to create your string to parse...

Sure, it'll work with any DOM/Language, just the interface/method/constants names may vary slightly...

You can just iterate through the children (IXMLDOMNodeList) checking the type (IXMLDOMNode::nodeType), if it is a text node (NODE_TEXT) append the value to your string otherwise keep iterating...

In your first schema you should change the xmlns:gns="http://localhost/XMLWebServices/GeneralFormatting.xsd" to xmlns="http://localhost/XMLWebServices/GeneralFormatting.xsd" so that all types declared are in that namespace, otherwise you would have to put the gns prefix on all type names...

You shouldn't be using the xs: prefix for the UserName type in the second schema, as the xs is for the schema namespace. You probably should define another xmlns for the imported namespace ie xmlns:gf="http:....GeneralFormatting.xsd" and then have

Maya is the application used by Weta Digital for "The Lord of the Rings" ie Gollum etc. I suggest you download the "learning edition" (http://www.aliaswavefront.com/freemaya[^]) and have a play before you get too carried away, 3d movies are not the easiest things to create especially if you are starting from scratch with no experience. The guys who made Shrek take two years per movie. Plus you need serious processing power (or patience) if you want to anything substantial Weta has over 2000 processors in its rendering farm (NZ Herald[^])

Attributes aren't part of the child tree as you are trying to use it. Attributes are considered separate by the DOM and need to be accessed via IXMLDOMElement::getAttribute or IXMLDOMNode::attributes, with the later being best for you usage as you can iterate over all available attributes.

If you write an XSLT style sheet you can use the MSXML (or most other) DOM to perform the transformation for you using DOMDocument::transformNode method...

Hey Bryce, you may want to check out the Rugbyheads website, it has a lively discussion board on all things rugby (southern hemisphere anyway) plus articles and our own pick-the-scores competition.

Maybe I am missing what Michael is getting at but I don't think he is entirely correct. The base64Binary datatype by definition doesn't require any replacements to be legal in an xml document as when it is encoded it uses the characters 0-9 a-z A-Z '+' '/' ie no replacements required see section 6.8 of http://www.ietf.org/rfc/rfc2045.txt for details (this page is linked to by the Schema spec). Also be aware that most XML DOM do translations required ie you set strings containing '>' '&' etc and they will automatically be converted on output to < and &, however I'm not sure if this is the case for binary types. If possible I would be tempted to use the hexBinary datatype as I find that easier to understand, two characters (0-9 a-f) are used to represent each hex octet ie 0x7f10 would be "7f10" in your XML doc. Hope I haven't confused you...

The MSXML DOM does the conversion for you & to & etc so you need not worry about it. However when you get a value out of the DOM it will not appear converted ie you will still retrieve &, the converted versions are there when the document is written to file or the XML retrieved with getXML etc

Film a reality TV series and make millions ;P

Check out http://www.steves-digicams.com/ for good reviews, I have a Fuji 2800, best bang-for-buck camera around IMHO, a little weak for shots at night though.