Sergey,

For me it shows it'll table scan the outermost table and do something it's calling a Hash Match/Right Semi Join for IN and EXISTS. For JOIN it shows a Hash Match/Inner Join. All with about the same expected runtimes.

>It's interesting to note that in SQL Server all three queries (IN, EXISTS and JOIN) most likely will produce the same execution plan. VFP query optimizer isn't that smart. :)