>I dont use hierarchical XML or recordSet for the moment but it's important to know all that. Thank you.
>
>For suggestions, i have one.
>
>When i send a SQL command with ADO, i receive a RecordSet. I know ADO give me a lots of object.command to manage the data inside the RecordSet. But here im a Foxpro programmer. I know all the commands in Foxpro to play with Cursors and my programs managed Cursors and it's very fast.
>
>In Foxpro 6, there is VFPCOM.RSTOCURSOR() give me the possibility to transforme a RS to a Cursor. I dont try it in VFP7, but in MSDN Library, there is 3 articles 1 for the reserved words, and the 2 others for bugs in convertions of types. In VFP7 Help, we have just the reserved words article. It's like something we suppose to know!
>
>I know there is a lots of programmers build there own programme to make the job like Dbf2Rs and Rs2Dbf by Ken R. Levy.
>
>Now Microsoft come with XML and make natives commands like XMLToCursor(), CursorToXML(), XMLUpdateGram(), XMLToObject() and ObjectToXML().
>
>Finaly, my suggestion is not realy around XML stuff. Just give us some fast natives functions like RecordSetToCursor() and CursorToRecordSet(). And please put it in the documentation.
>
>You do it with XML, it's because there is a need? Why you don't do it with RecordSet all those years?
>
>Sorry, a little bit angry ;)
>
>Maybe i miss something,
>
>Explain to me,
>
>Francois Durocher
Francois,
'Reserved' words mean that they 'might' be used in future versions (just probable placeholders). Keywords OTOH are really there.

Now to add your question I always wondered why we should ever to go over ADO when it's a fox tech :) (If I'm not misinformed it's a fox team success)
I always also thought why remote views only use ODBC. Simply I don't like ODBC but OLE DB.
Yes ODBC, ADO, RS2cursor and reverse operations are slow :( Anyway I like it's getting better and better.
Cetin