>All of the problems are apparently now solved. Certain queries process slower than others (ex. featper.cfeatper is the only criteria I ask, but I would expect this condition w/out additional criteria.
>
>I was not aware that my JOINS were in a nested condition. I used the Query builder to create the basic syntax. How is the processing different between what you suggested and what VFP built ??
>

This is a known problem with the View Designer. The VD always nests the joins which can [and usually will] cause problems. So most of us use the VD to create the initial SQL. We then view the SQL in the VD SQL viewer, drag the mouse over the generated code and hit CTRL+C. We then copy this into a PRG file, modify it, then run it to create the view. You can then use eView or GENDBC.App found in the HOME() + "TOOLS\GENDBC" folder.

I believe nested joins work if the join types are different. There are probably other deciding factors, so I just un-nest them from the beginning.