Will we be able to create compatible XML files that can then be picked up as an XMLDataSource?

>>What are the possibilities of seeing Sedna tackle creation of something like the XMLDataSource, that can be bound. I think having a good way of databinding between the UI's written in Avalon (and other strategic technologies) and a VFP COM/Database backend (still want to be able to massage the data with VFP) would be nearly a necessity. Are there any ideas floating around on this, whether in MS or here on the UT?
>
>Creating something new native to the core VFP EXE/DLL is not something in the scope of our efforts on Sedna, but enhancing existing components such as the XMLAdapter as needed for meeting our goals (scenario driven) is possible. We looked at native XML databinding in the past and found the best solution is to convert XML to VFP cursors (via XMLAdapter) and then databind like usual (just like with native DBC/DBF data). Another option is to have .NET code in an Avalon form connect to VFP data via the VFP OLE DB provider. Via XML to/from an ADO.NET dataset and the VFP XMLAdapter class is about the same for an ASP.NET web page, .NET WinForm, and an Avalon form.