David, Many thanks - that did the trick - I have an executable. The downside -
something I didn't realise - was that to have a static build of Xerces
included, then I need to have a static build of the whole MS MFC environment.
I really only wanted the former, so that I did not have to distribute Xerces
with the application. I think I will need to re-think this approach. Maybe I
will try the 'perfect parser' approach mentioned by Jesse when I first started
this migration from MS XML to a schema validating XML parser that was available
on more than one platform .. but I fear this is going to be a subject of more
messages in a different user group.
Again, thanks for all the suggestions - really appreciated.
David
PS. As an aside, in case I do go back to this. I have a weird problem both in
dynamic and static builds. The parsing and schema checking works fine but, if
I have a certain complex element in the schema [irrespective on whether the XML
file has any of them], I get 4 memory leaks on program termination. The schema
checks out with all the online validity checkers, MS XML doesn't complain -
just these 4 memory leaks with Xerces. Take out the optional element
(minOccurs = 0) from the schema - no leaks, although obviously I can't import
XML file containing these elements. I modified SAX2Print example to use my
schema, XML file and all the same SAX2 features and properties, but it didn't
have the problem. As I said - weird!
_________________________________________________________________
Win an Xbox 360 or £200 Top Shop Vouchers
http://clk.atdmt.com/GBL/go/115454062/direct/01/
