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
|
|||
|
|||
show duplicates of 2 tables
Hi,
I have 2 table which have identical fields and I wish to create a table from the duplicates found. The wizard does the opposite it takes out the duplicates. How do I go about it? Cheers -- Paul Wilson |
#2
|
|||
|
|||
show duplicates of 2 tables
On Tue, 12 Feb 2008 15:37:00 -0800, Paul Wilson
wrote: Hi, I have 2 table which have identical fields and I wish to create a table from the duplicates found. The wizard does the opposite it takes out the duplicates. How do I go about it? Cheers Create a Query joining the tables on *all* the fields which define a duplicate; change it to a make-table query. Why you would want to store data that is already twofold redundant in THREEFOLD redundancy is beyond me! What on Earth are you trying to accomplish? -- John W. Vinson [MVP] |
#3
|
|||
|
|||
show duplicates of 2 tables
The client wishes to see the 2 sets so they can fix up there database. To
minimalize re-occurence. Thats seems to do the trick with exact matches, is there a way to make it not so exact on matches? Thanks John. -- Paul Wilson "John W. Vinson" wrote: On Tue, 12 Feb 2008 15:37:00 -0800, Paul Wilson wrote: Hi, I have 2 table which have identical fields and I wish to create a table from the duplicates found. The wizard does the opposite it takes out the duplicates. How do I go about it? Cheers Create a Query joining the tables on *all* the fields which define a duplicate; change it to a make-table query. Why you would want to store data that is already twofold redundant in THREEFOLD redundancy is beyond me! What on Earth are you trying to accomplish? -- John W. Vinson [MVP] |
#4
|
|||
|
|||
show duplicates of 2 tables
On Tue, 12 Feb 2008 17:04:06 -0800, Paul Wilson
wrote: The client wishes to see the 2 sets so they can fix up there database. To minimalize re-occurence. That's what I don't understand. You will now have three different tables containing the same data. Any or all of the three tables can be edited. You now have many MORE opportunities to screw up the data and have two or three different versions in three different tables. What benefit do you see coming from creating the redundant table... again? Are you perhaps making the common but erroneous assumption that you need to create a Table in order to create a Report? Thats seems to do the trick with exact matches, is there a way to make it not so exact on matches? Probably. But my telepathy is a bit on the blink tonight and I don't know what your data looks like or what constitutes a "not so exact" match. -- John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|