V6 Optimizer?: Query based on view

I'm trying to analyze the (poor) performance of a Forms detail block query based on a view. When I evaluate the view alone using EXPLAIN PLAN (join of four tables) I've got a full table scan on one table, indexes for others. If I add the criteria that comes from the master block in the Form, then I use indexes on all four tables.

??: How do I know which is the situation that occurs when the Form is actually being used? Is the result of the view stored temporarily in which case there would be no index on the master-detail block column applied, or is the screen criteria "tacked on" to the end of the SQL statement when the view is parsed, thereby (maybe?) using all four indexes?

rchance_at_netcom.com Received on Fri Oct 15 1993 - 15:59:02 CET