>Hi All:
>
>Has anyone thought about using XML rather than ADO as a messenger? I have been experiementing with building some classes to handle XML conversions. Using XML, you can leverage the power of VFP's local cursor engine without the overhead of ADO. Its even really easy to create relational XML from VFP tables engaged in a relation. On the client side, you can use the XMLDOM to populate controls directly, or convert it back to cusror. It all very flexible!
>


I am extrememely pumped about XML but have had my fire doused a bit by the fact that we can't distribute XMLDOM. Ok, we can- but the machine has to already have IE4 SP1 on it. I can't force a browser on somebody because of my app's interna; messaging scheme. I tried.

>The really cool thing about XML is the application of XSL templates. XSL is an extremmly powerful tool for transforming XML for layout. To me, its alot like what we try to do with the VFP report writer, but much more powerful.
>
>I have thought of some other uses of XML, like replacing INI files or registrty entires and parameter passing.

Parameter passing, I can see. But Registry entries? Why? The registry already gives us the flexibility we need...