>What do you know about how VFP handles SQL internally? Right, nothing (the
>same apply to me too ;).

:) You're right. We don't know much about the implementation of SQL in VFP. But we can make tests. And in this kind of problems, I never saw one that is faster when is done in 2 steps. This is why I asked you: to be sure that what I observed is correct.

> I know how to speed up SQL with Rushmore (if it's
>simple), but I know nothing about how VFP handles Union clause or nested
>selects. May be it's my personal habit, but I like do calculation process
>step-by-step, it could be more understandable after two-three month...;))),
>After all, this doesn't matter ;)

It matters a lot. And I agree that sometimes you can/must trade performance for readability. But this doesn't mean readability = performance. :)

Vlad

>
>* Will write login scripts for food
>
>>Why are you so sure? Do you have a case for it? I never could get a
>faster
>>program using 2 SELECTs when I could use one embeded into other. This
>goes
>>for cases similar to the one discussed here. It's true that for other
>cases
>>you may have a better performance if you can separate.