|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
November 22nd, 2006, 05:23 PM
posted to microsoft.public.access.queries
|
|||
|
|||
Query query ...
I have two tables, both linked on Customer Code.
To isolate the items that are common to both I use a straight forward query (it uses an Inner Join) To isolate the rows that are in one but not in the other (to create an update query) I use an outer join, displaying the "Customer Code" from both tables. When I do this I can identify the rows that are not in the first as they show a blank customer code. Is it acceptable to filter this table by selecting a criteria of "is null or 0" on the second "Customer Code" is there a better way to identify records in one table that need to be inserted into the second because they don't currently exist. jON 
|
|
#2
November 22nd, 2006, 06:33 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Query query ...
You are doing it the way I would suggest.
Jon Rowlan wrote: I have two tables, both linked on Customer Code. To isolate the items that are common to both I use a straight forward query (it uses an Inner Join) To isolate the rows that are in one but not in the other (to create an update query) I use an outer join, displaying the "Customer Code" from both tables. When I do this I can identify the rows that are not in the first as they show a blank customer code. Is it acceptable to filter this table by selecting a criteria of "is null or 0" on the second "Customer Code" is there a better way to identify records in one table that need to be inserted into the second because they don't currently exist. jON
|
|
#3
November 22nd, 2006, 09:41 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Query query ...
Great thanks Jeff.
regards, jON "Jeff L" wrote in message oups.com... You are doing it the way I would suggest. Jon Rowlan wrote: I have two tables, both linked on Customer Code. To isolate the items that are common to both I use a straight forward query (it uses an Inner Join) To isolate the rows that are in one but not in the other (to create an update query) I use an outer join, displaying the "Customer Code" from both tables. When I do this I can identify the rows that are not in the first as they show a blank customer code. Is it acceptable to filter this table by selecting a criteria of "is null or 0" on the second "Customer Code" is there a better way to identify records in one table that need to be inserted into the second because they don't currently exist. jON
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
