[AccessD] NOT Query.

How about another query with a left join from query B to query A, and pull
only the records where    queryA.Clients is Null, ie:

SELECT QueryB.Clients, QueryA.Clients
FROM QueryB LEFT JOIN QueryA ON QueryB.Clients = QueryA.Clients
WHERE (((QueryA.Clients) Is Null));

HTH

Rusty

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Monday, March 30, 2009 5:33 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] NOT Query.

EXISTS?

http://www.devx.com/dbzone/Article/9570/1954

Susan H.


> Thanks Max - And i was just looking at (NOT IN) and thinking  "oooh, 
> that looks useful" :)  noted!.
>
>
> Darryl,
> Do not use the NOT IN clause if you can avoid it.  It is extremely 
> slow on large datasets.  The quickest way was given to me (I think by 
> Jim) some time back but I cannot recall it and don't have time to go 
> searching right at this moment.
>
> I have two queries.  Query A and Query B both contain a field called 
> Clients (Based on the same underlying data).  A and B correctly return 
> a different number of records in the client field.  I want to be able 
> to list which clients are in query B that are missing in Query A.  
> Basically I want the opposite of joining the two queries based on the 
> clientfield.
>

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

**********************************************************************
WARNING: All e-mail sent to and from this address will be received,
scanned or otherwise recorded by the CPI Qualified Plan Consultants, Inc.
corporate e-mail system and is subject to archival, monitoring or review 
by, and/or disclosure to, someone other than the recipient.
**********************************************************************