The difference in the estimate and actual recordcount is the result of the combination of the inner join and the AND clause in the table join if that makes sense. The WHERE clause filters the main set of records being queried on the inner join. If I use a left join I would return the same recordcount with NULL values in the second table. There's probably a lot smarter way of approaching this but that evades me... obviously, but I am learning.

This is the base table view for asset attributes that will link to a GIS table on a different server and database to create a spatial view I have about 70 to do. All records are required in the join to the table in the GIS db. At the moment all records will be updated into a GIS table for all the mapping applications to use both internally and the web. The update should be each night.

I appreciate your assistance.

Bruce.