You may find other XML validators that better fit your needs, this doesn't needs to be anything integrating into VFP as it's really a very seperate problem. I have to admit I didn't used any of those, yet.

Perhaps use Notepad++ ( )or Liquid XML Studio ( ). Parsing and validating XML and pointing out and describing errors.Īs XML/XSD/DTTD and further related file types are text files you are not depending on tools capable to work with VFP variables, objects, classes, code etc and so ae free to use anything online (eg Well, I am not an expert on XML, the only really good source of XML handling in VFP is wwXML from West-Wind, if you want something foxpro specific, but I don't see how it includes That already brings me to the second question about other tools to validate XML. Whilst it is a 64-bit operating system it has a 32-bit compatibility layer which old applications use to run. At the time of writing the latest release of Windows is Windows 10. New hardware and software bought today are all using a 64-bit architecture. Each of these new features is covered in detail so developers can be productive right away. Visual FoxPro is built on 32-bit architecture. Like w3c validators do for html errors, for example. Visual FoxPro 8.0 features improvements in many areas, including several new base classes, structured error handling, and several new tools. That would mean many follow up errors, which would not be errors, if the first error would be solved, so sometimes it would be futile to know more than the first error, but often enough errors are uncorrelated and could be reported in a batch list of errors, It would make sense to know further errors, sometimes The XMLAdapter just wraps around MSXML2.DomDocument.4.0 and it's LoadXML method just calls the LoadXML of MSXML2.DomDocument.4.0, which in my knowledge just stops parsing on the first error detected. Muthu quite surely has found some solution on his own or at another place.īut since this question may be of more general interst:

Microsoft visual foxpro 8.0