By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,165 Members | 1,089 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,165 IT Pros & Developers. It's quick & easy.

Unique Fields

P: n/a
I have a rather sizeable mailing list with several fields. I need to
filter out records with duplicate address fields (spouses and
families). I've had no luck using the advanced filters tool - any
suggestions?

PS: Another small problem is that some duplicate addresses differ only
because one has a period to abbreviate "road"/"court"/"lane", and the
other does not. Any help on this would also be appreciated.

Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On 19 Jul 2005 22:24:07 -0700, da**********@gmail.com wrote:
I have a rather sizeable mailing list with several fields. I need to
filter out records with duplicate address fields (spouses and
families). I've had no luck using the advanced filters tool - any
suggestions?

PS: Another small problem is that some duplicate addresses differ only
because one has a period to abbreviate "road"/"court"/"lane", and the
other does not. Any help on this would also be appreciated.


It looks like this may be helpful to you -
http://www.usps.com/ncsc/addressserv...correction.htm
Nov 13 '05 #2

P: n/a
Hi Danie,

To answer the first problem briefly, you could probably run a query on
the data set you have, by doing a SELECT DISTINCT
[tblPeople].[Address], plus all the other fields. This would return
records with only unique addresses. There are a few considerations you
should take, though:

- How is your address set up? Is it just the street number + street
name? If someone in another town lives at the same street number AND
street name, then you might have a problem.
- Also with regards to your second problem with the duplicate address
differences...you would probably need to sort this out somehow manually
(and standardise the addresses), or follow Steve's suggestion(which I
think costs something). Otherwise my suggestion to the first problem
will not work.

I have in the past had a similar problem, where I was advised to
normalize my tables. I am not saying that this is the only option, but
it could possibly enhance the design of your DB. What you would do is
have a table set up where you could keep track of who is related to who
in your tblPeople. I cannot remember the exact procedure for doing
this, but I could have a look in one of my textbooks at home.

Hope that helps a bit.

Regards

Jean

P.S. Are you Sakkie?

Nov 13 '05 #3

P: n/a
Thanks for the help, Jean. As of right now, I'm stuck exporting the
contents of the DB to Excel and manually removing the 680-some
duplicate addresses. I'll follow your suggestion to standardize the
system, though.

Sakkie?

Danie

Nov 13 '05 #4

P: n/a
Maybe someone has a better solution, if you check here once in awhile,
you might be lucky...

If you need to, just do a search on "database normalization"

I just thought you were someone I knew from Stellenbosch, South Africa.
You have the same name, and I think we used to call him Sakkie. Oh
well...

J

Nov 13 '05 #5

P: n/a
Well, I'm from Cape Town, SA, myself. Always a plus encountering a
local.

Cheers

Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.