>>I have stated that I would be easily willing to give up macro substitution if
>>we were given a few key things in exchange: a substitute for functions that
>>take only literals instead of named expressions (certain SET commands), and a
>>way to execute SQL expressions (a substitute for &lcSQL).
>
>RecordSet.Open(mySQLCommand)

But that doesn't give me a VFP cursor. And I can't use it on cursors at all.

Or were you just being funny? :-)

There is also SQLEXEC() but I don't have to tell you that using the ODBC driver to access VFP data is not the way to go...