J
Jon Rowlan
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
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