Johan,

>>error XS0103: The name 'createobject' does not exist in the current context
>Can we keep errors/warnings to the X# forums?

Certainly. Does createobject work in your version ? Guessing that you are one up to me.
>
>Have a look also at https://github.com/mattslay/Visual-FoxPro-Toolkit-for-.NET before you re-invent the wheel...

Did look. Inconsistency in first one I touched - see on xSharp. Might have another idea, but depends to a large degree on ability of xSharp to execscript or compile snippets.
>
On steps:
- Definition of compliant but Esperanto-SQL, no building of parser needed, just rules followed concerning keyword order, loading into correct lists
- building Single-table SQL result, without aggregate funcs, having, order processed as first result
- building Inner-join SQL result, join in join or where, without aggregate funcs, having, order processed
- building Left-join SQL result, join in join or where, without aggregate funcs, having, order processed first
- building SQL result for Queries including including aggregate funcs, having, order, field/table alias optional
- deciding on mechanism for Buffering [Table, Cursor] mode=Tablebuffering, as Row can be handled w. scatter
- CursorAdapter as eagle-eye blueprint, checking out ADO.Net (with an eye out for reusing parts on remote views)
- implementing iterator for tableupdate able to work in xBase or SQL - needed if talking to SQL backends
- Tablereverse, secure blocking of cursorrefresh on unsaved changes and other small fry
- CursorAdapter event handling
- update strategy on ts and writecounter first
- others in interest exists

Nice full dozen as of now. Aggregate SQL could be implemented 1 or 2 steps earlier.
Tableupdate steps could be done earlier and/or interweaved with SQL steps, but need to keep that order
Last steps fixed. Comments ?

regards
thomas