How do you delete duplicate records in Paradox 7

I am using paradox 7 I have inherited a database which
has about 6500 enteries. I have noticed that there is a number of duplicate records but I can not see a way to
get rid of these. There is three keys which I would like to check (phoneres, Fname and Lname) if these three fields combined are identical I want to get rid of the entire record.
paulandersonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

paulandersonAuthor Commented:
Adjusted points to 100
0
cymbolicCommented:
I am not a Paradox guru, but let me describe a general technique that you may be able to use.  It involves a multiple step process.

1). You create a view that is sequenced on your duplicate keys, grouped by your keys, and you create a calculated field that is a count of each member in an identical group.

2) You can now identify your duplicated records as only those with a group count greater than one.

3) You can create another view with only dupe keys. Then use that view to join/delete against your original table.

4) If you want to insert back one of the duplicates, make sure you include all the original columns in you table, then after deleting all dupes, you can insert back one from each duplicated group by using your sequenced and grouped view from step one.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cemaylorCommented:
You could perhaps save a database file, and do the indexing as proposed by cymbolic, do a sequential pass thru the file, comparing current record to last record, and dump any which are dup's.

This requires no counting and requires only one pass through the data.

Cheers!

Chris Maylor

0
cemaylorCommented:
You could perhaps save a database file, and do the indexing as proposed by cymbolic, do a sequential pass thru the file, comparing current record to last record, and dump any which are dup's.

This requires no counting and requires only one pass through the data.

Cheers!

Chris Maylor

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.