>>>I hope not, and that someone will tell me where's the switch to turn this on.
>>
>>Can you use derived tables?
>
>Maybe, but what after? That would complicate things, though, because these would then be free tables and I have many fields with long names; I could create a temp database and send intermediate results there... but, again - cleanup? This is supposed to be something I can give to the Access guys, with "here's your script, just run this and you'll have your recordset". I've done this for other such cases, but for pulling data from SQL server, and there was no problem.
>
>Besides, creating a temp database etc - wouldn't that involve some heavier scripting and teaching the guys I've never seen some VFP tricks? I just want to have
>
>select ...from table1 join table2 on ... join (select something from table3 where ...) alias3 group by... etc.etc... into whatever1
>
>select ... from myothertable join whatever1 on {some condition}
>
>and have the results of the 2nd select in a recordset.
>
>Writing a little app which would export the data is also not an option - it would involve installation, distribution, maintenance etc, again not viable.

My point is that the whole select can be done as few derived tables, e.g.

select ... from myothertable join (select ...from table1 join table2 on ... join (select something from table3 where ...) alias3 group by... etc.etc... ) X on ...