Nubian,
Without any specific information about your table/fields, that would be
hard to say.
Give us a bit of info about the relevant fields in your table, and... how
you would determine that a record is a duplicate or not. Then we might be
able to find some logic to assist in their removal.
As a general rule though, dupes uaually can't be found
"automagically"...
John V. Smith 37 Main Street....
and
John V. Smith 37 Main St....
and
John Smith 37 Main Street.....
None of these records would "logically" qualify as a duplicate.
Unfortunately, this is where the human brain has to be applied, to make that
decision.
So finding dupes is usually human manual comparing and editing.
AND...
It is better to try to avoid duplicates up front, at user entry time,
rather than hunt them down after the fact.
Something like...
You just created a new record with LastName = "Smith", and FirstName =
"John". If, at that point, you show the user all the records you have
already, with Smith and John would help them decide if the new record is a
dupe or not.
Of course, this is not perfect, and is used an example of how you...
using your own logic, can help prevent dupe entries at new record entry.
--
hth
Al Campagna
Microsoft Access MVP
http://home.comcast.net/~cccsolutions/index.html
"Find a job that you love... and you'll never work a day in your life."
