Remove Duplication

1. Sharron Lily Guest

## Remove Duplication

Hello Friends ,<BR>This is my first time at this site reffered by a friend i hope you guys could help me out.<BR>I have a table in MS Access having many fields.<BR>The fields are Part_numbers,Office,Pool_ID,Bin_Location,ESC...etc .<BR>There are 7000 rows.Out of this 7000 rows around 2000 rows contains duplicate part_numbers.I want to remove the Duplication of part numbers. example..<BR>Below Table name is &#039;Inventory.mdb&#039;:<BR>--------------------------------------------------------------<BR>part_numbers, Office, Pool, Bin, ESC,... <BR>--------------------------------------------------------------<BR>00436-60008, D400, J9013, XYZ, \$500<BR>00436-60008, D476, J9014, XYZ, \$500<BR>__________________________________________ ____________________<BR>Maximum number of repeatation of a single part_number is three.<BR><BR>SO WHAT I CAN DO IS,mearge the table i mean, i can have additional fields like Office_2,pool_2 and so on. ie...<BR>&#039;Solution.mdb&#039;:<BR>--------------------------------------------------------------<BR>part_numbers, Office, Office_2, Pool, Pool_2, Bin, ESC . <BR>--------------------------------------------------------------<BR>00436-60008, D400, D476, J9013, J9014, XYZ, \$500<BR>__________________________________________ ____________________<BR><BR>For getting the above (which is my requirement) i have to first create two or three tables from the inventory table and keep all the duplicate part_numbers row in different tables.Then run a query to get a common solution.mdb table.<BR>So my question is how split the &#039;first table ie.. &#039;inventory.mdb&#039; in to two or three tables on the basis of the duplicate part_numbers.Tell me if SQL alone can solve it without using ASP(even better).Else how to do it using ASP.My database is of Access.<BR>Regards and Love,<BR>Sharron Lily.<BR><BR><BR>

2. Senior Member
Join Date
Dec 1969
Posts
96,118

## That would be BIG mistake!

As it stands, you *ALMOST* have a *NORMALIZED* database.<BR><BR>It would be a *BIG* mistake to turn it into an UNNORMALIZED database, as you are asking to do!<BR><BR>What *possible* reason do you have for destroying the proper layout of this table?<BR><BR>How many fields in these "duplicate" records (and they are *NOT* duplicates! You are very wrong to think of them that way!) are 100% identical in all "pairs" of records? Only one? If so, the DB is perfectly normalized. A couple? Several? The more perfectly identical fields there are (and remember, that means in *ALL* of the paired records!), the more the DB could stand a *little* work. But *NOT* what you are suggesting.<BR><BR>I can&#039;t think of one good reason to do what you are suggesting. Do you have some excuse?<BR><BR><BR><BR>

3. Sharron Lily Guest

## RE: That would be BIG mistake!

Bill First of all Thanks a lot for your reply.But i really need to UnNormalize the table.As i am creating a Virtual Stocking Model so i cant have more than one row for the same part_number.<BR>So can you help me UnNormalize the table?<BR>Love<BR>Sharron

4. Senior Member
Join Date
Dec 1969
Posts
1,505

## CROSSPOST--BIG TIME!!!!!!!!!!!!

this is the 4th place she has posted her question, what&#039;s up with this lady?

5. Senior Member
Join Date
Dec 1969
Posts
96,118

## It is *STILL* a mistake.

I think you are confusing *reporting* data in a DB with the *contents* of the tables in a DB. <BR><BR>So stop crossposting, try listening to some of the advice you are getting, and *learn* about how *good* db&#039;s are designed!<BR><BR>And what in the world is a "Virtual Stocking Model"???<BR><BR>

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•