Yes, it's a good discussion.

Eric has some good insights & experience on it as you do with ADO. Some folks have concerns and are confused with respect to ADO vs XML (in addition to the normal havoc created with VFP vs VB discussions).

Although you and Rick have some excellent articles on this, it would be interesting to see a more detailed analysis of the comparison of the two technologies (e.g. how/when/where to use ADO vs how/when/where to use XML).


>I don't think it will lose appeal. It is about the most flexible thing out there. It can be anything you need it to be...
>
>I think it's application lies more in messaging than in transfering data. Sure, you can transfer data. But, ADO provides the structure required when working with data. For example, when needing to update, XML cannot do it alone...
>
>This is a good discussion...
>
>
>
>>This is interesting. It seems that XML messaging is the beginning of a type of hybrid data protocol.
>>
>>The overhead is a function of the amount of data being created and parsed and is a design issue for the developer.
>>
>>I'm just wondering about XML's long term viability with respect to increased bandwidth capacities in the future. Will it lose it's appeal?
>>
>>
>>>Another nice thing about using XML as a messenger is being able to use XSL to format data. I did a little experiementing with this technology and was very impressed, although it was hard to understand. I wonder if there is any potential for using XML\XSL to replace the Report Writer in VFP?
>>>
>>>The biggest problem I see with using XML as a messenger is the overhead involved in creating and parsing it, this obstacle may limit XML's viablility.
>>>
>>>Charlie