Kerry


SELECT INTO creates the table for you.

Roy Lambert

Kerry,

<< Anyway, if you can see a faster way to run the query, I would appreciate
it. >>

Well, the issue is what I thought it was originally.  The
userauthority_offices condition in the WHERE clause doesn't filter any rows
for the joins because the join is on the OfficeID column, therefore the
query has to perform ~35,000 X 4 X 2 joins in this query to generate the
result set, or ~280,000 joins.   That's what is taking so long.

The only solution is to filter the rows a little better by being more
selective in your criteria for the WHERE clause.  If that's not possible,
then you'll have to live with the execution time.

When I get a chance, I'll migrate the data and run it against EDB and see
how fast it goes.

--
Tim Young
Elevate Software
www.elevatesoft.com