Heenan, Lambert
Lambert.Heenan at AIG.com
Thu Jul 24 09:30:08 CDT 2008
Oops that should be... SELECT DISTINCTROW SomeTable.ID, SomeTable.dDateAcknowledged FROM SomeTable LEFT JOIN SomeRelatedTable ON SomeTable.ID = SomeRelatedTable.FkID WHERE (((SomeRelatedTable.FkID) Is Null)); Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert Sent: Thursday, July 24, 2008 9:57 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] SQL - Alternative to using NOT IN Clause A field *value* that shouldn't/doesn't exist. Like so... SELECT DISTINCTROW SomeTable.ID, SomeTable.dDateAcknowledged FROM SomeTable LEFT JOIN Policy_Pipeline_tbl ON SomeTable.ID = SomeRelatedTable.FkID WHERE (((SomeRelatedTable.FkID) Is Null)); Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Thursday, July 24, 2008 9:48 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] SQL - Alternative to using NOT IN Clause What? A field that shouldn't exist? Susan H. > Make it a left or right join, and then put Is Null in a field that > shouldn't exist in the table missing records. > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com