<< I think, I heard somewhere that "in" is not good for speedy selects. Is there something though that is better to use for "not in"? >>
IN is very fast, it does use indexes. NOT IN doesn't use indexes (similar to the way in which = does but <> doesn't). << The following select statement seems to take awhile to do a count. >> To optimize your SELECT statement, you'd have to include: 1. The view definition for vwBGProjectInfoTopLevel 2. The contents of the variable fNewST -- Larry
