David,

Your explanation is clear and logical; you are good explaining things, like a professor. :)

I believe that the strictness is hurting the tool; perhaps we need an additional flag to tell it to relax and try its best:

x=CREATEOBJECT("xmladapter")
x.RelaxAndTryYourBest = .T.  && LOL
x. LoadXML(lcXMLDocWithLittleSchemaCaseProblems)

… or a new “AnalizeSchema” method that can tell us if there are schema validation issues instead of the “schema too complex” message.

Both Internet Explorer and the XMLDOM are able to load that XML doc without a problem, as the Latin American saying goes “why do we need to be more papists that the Pope?”

Thanks again,

>David,
>Perfect, it worked, thanks for clarifying Aleksey's answer.
>Great questions for Aleksei too, I'm really curious about those.
>
>Aleksey, please disregard my second message.
>
>>Aleksey,
>>
>>>XDR schema doesn't define datetime data type, it defines dateTime data type (case is important).
>>
>>Good info for Maximo, so he can just:

x=CREATEOBJECT("xmladapter")
>>? x.LoadXML(STRTRAN(FILETOSTR("zambrano.xml"),"datetime","dateTime"))
>>x.tables(1).tocursor()

So this is an example where something incorrect in the Schema definition results in the error message: "XML Schema is too complex."
>>
>>In what other circumstances does that error message occur? Is it mostly due to something wrong with the schema, or are there schemas that really are too complex in structure (and not just containing an error). In other words, is this error message one that catches all problems in interpreting a schema, whether or not the schema is really valid?
>>
>>Thanks for any clarification you can give...