Cristof-

Right-o. I don't do data either. Or at least I make sure EVERYBODY is sorry if I *have* to...LOL. I thought you meant that a SELECT statement against a xBase backend will optimize but against an Oracle Database (for example) wouldn't.

I agree with the LIST FOR and SELECT difference. Again, my note was only informational. The command was a revelation to me :-)

>>Since, I have the luxury of being--to date-- all xBase, I wonder what one can do for optimization against non-xBase backends? Or would one concentrate more on using FetchSize (?)?.
>
>I've no idea, I don't do data. *g*
>
>What I meant is that SELECT issued against a local table and LIST FOR (or any other xBase command) issued against a local table use different optimization engines. For example, NOT == is optimizable in xBase, but not in a SELECT statement, functions are treated differently, and with SELECT, SET ANSI comes into play...
>
>Christof