I am currently using web connection (killer product BTW) to build thin client applications (the app server generates HTML). I have also been experimenting with VB activeX front-ends with the data delivery being XML from the app server. Admitedly it is an easy solution to implement. But with relational data there seems to be a pretty significant portion of data transmitted (column headings) that is unnessacary overhead.

Because the intrinsic structure of relational data is the same for every table (every table has rows and columns) it doent seem like XML is a good fit for transporting relational data. If one was using a multidimensional database XML would make more sense. The data structures (nodes, sub-nodes etc) would change depending on the data requested. So it would make more sense to send the quasi-schema with the data (as XML does).

I see XML as a good fit for interoperability between systems. Its not bad as far as an industry standard. Standardization is key for interoperability. But most business system operate on thier own internal relational data stores.

If all I want to do is transport my relational data to the front end I don't see the benefits to XML. If I want to interface with externalsystems XML seems like the standard we have all been waiting for.

Just my 2 cents

Peace
Jon